OBiTALK Community

General Support => Installation and Set-Up (Devices) => Topic started by: omuskie on June 10, 2012, 09:07:20 PM

Title: digimap wrong decision?
Post by: omuskie on June 10, 2012, 09:07:20 PM
I've this setup under the ITSP Profile A's digitmap:

(1416xxxxxxx|1647xxxxxxx|1905xxxxxxx|1800xxxxxxx|<**2>xx.|(Mipd)|[^*]@@.'@'@@.)

But sometimes, system make the call to 1416xxxxxxx or 1647xxxxxxx thru the SP2 (<**2>xx.). Any idea? Thanks!
Title: Re: digimap wrong decision?
Post by: pc44 on June 11, 2012, 05:42:21 AM
Hi omuskie,

Are you always entering the 1 at the beginning of those numbers?  For example, 1416........ instead of just 416........?

Just checking,
pc44
Title: Re: digimap wrong decision?
Post by: omuskie on June 13, 2012, 02:27:25 AM
Yes, always with "1".
Title: Re: digimap wrong decision?
Post by: ianobi on June 13, 2012, 05:51:57 AM
The GGOD (Great Guru of Digitmaps) never liked to see xx. in a digit map as it matches all the other rules in the same digit map. Rather, use <**2>(Msp2). Then you can maybe be more specific in Msp2 to avoid any accidental matching in your ITSP Profile A's digit map.

I'm not in North America so I won't try to to provide in depth details.

Good luck!

ianobi