Digitmap not working as expected for international and 900 blocking
RajR:
Hi Experts,
I just started with an OBi110.
SP1=Google Voice
SP2=Localphone
Primary line = SP1
My goal: All USA calls go via SP1 (GV), all international calls go via SP2 (Localphone) without 011/00 prefix (provider requirement). Also, block all 1900 premium numbers and route 411/911 to appropriate destinations. Here is my digitmap that ALMOST works (no other settings changed):
User defined (ste): (<911:14082993233>S0|<411:18003733411>S0|!1900xxxxxxx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1650>[2-9]xxxxxx)
SP1: (<**2><00:>xx.|<**2><011:>xx.|(Mste)|(Mipd)|[^*#]@@.)
SP2: ((Mste)|xx.|(Mipd)|[^*#]@@.)
Issues:
1. Dialing a 1-900 number via SP1 (GV) gives a fast busy tone (good/expected), however dialing the same via SP2 (prefixing **2) the number attempts to get routed and fails with a 404 error. I was expecting the Obi would not even deliver the number to the SP2 and give a fast busy as well, which is not happening. Is this an issue with the digitmap?
2. Is there any way to modify the digitmap to allow selective international number dialing using SP1 either by prefixing with **1 or some other means... without having to change digitmaps?
3. Is the digitmap shown above ok or any way to write them better or as per recommendations? For example, I had initially tried <**2><011:>011xx. for dialing 011, but that did not work, instead removing the 011 prefix worked, but I am not sure why.
4. Newbie GV question: My GV Inbound calls ring fine but it does not ring the other forwarded phones setup in GV. Is there some way to control the delay after which Obi handles the GV call so other phones also ring? This is now working. May have been a GV glitch.
Thanks!
Raj
RajR:
Update: I am not sure the barring is even working. To test it, I replaced the "!1900xxxxxxx" with my cellphone e.g. "!16505555555" and it still rang the phone! So Is there something wrong in the digitmap? Should the barring numbers be directly inserted in the SP digitmap versus a user defined one?
Please help!
Thanks.
ianobi:
User defined (ste) can be a good idea if you need a lot of the same rules in different DigitMaps. Are you sure that applies here? It seems that the two DigitMaps should be doing very different things.
This does not answer all your points, but try it and come back with your thoughts and we can probably work the rest of your points out:
sp1: ((Mste)|<**2>00xx.|<**2>011xx.)
sp2: ((Mste)|<00:>xx.|<011:xx.>|xx.|(Mipd)|[^*#]@@.)
Be careful with rules such as xx. and [^*#]@@. As far as digits are concerned they both match any digit followed by any number of digits. [^*#]@@. Can be improved by changing to [^*#]@@.'@'@@. Or just remove [^*#]@@. If you are not using sip uri dialling in that DigitMap. I have removed (Mipd)|[^*#]@@.) from sp1 as GV does not allow sip uri dialling.
Edit: <011:xx.> should read <011:>xx.
carl:
Just to remind you that Localphone allows for outgoing number blocking , that should take care of the 900 problem.
RajR:
Thanks Carl - the localphone outgoing number blocking is what is getting kicked in and not allowing the 900 calls. However, I wanted to stop it at the source in case other providers don't support it. Hence wanted to try the the "!" barring feature.
Ianobi - thanks for the suggestion - I will try it out tonight and let you know if that works. I like the separation of concerns with your suggested digitmap. btw, the xx., Mipd and all that ^*@ stuff is something from the default Obi settings which I just left as-is. I will remove it as you said.
Re. (ste), since both sp1 and sp2 needed the same seven-ten-eleven routing, and also the 911/411 routing, I put that in the user-defined setup and assigned to both SPs. Apart from the international routing, is there any reason you see that the custom (ste) should NOT be reused in both SPs?
Thanks
Raj
Navigation
[0] Message Index
[#] Next page