Setting up Obi110 for Brazil PSTN + GVoice + SIP
Breno:
Hello, I bought an Obi110 and have it currently setup for usage with my PSTN line, Google Voice and FreeVoipDeal (a betamax provider).
Everything is working fine besides some latency.
I fixed my caller id problem by changing the line port calleridmethod to dtmf, and the tone by this topic - http://www.obitalk.com/forum/index.php?topic=2015.msg12744#msg12744
I also managed to reduce the delay a little by using some tips from here - http://www.toao.net/500-mangos-guide-to-configuring-an-obi100-obi110-and-obi202-ata
But Im trying to get a proper Digitmap to work but so far i got no success.
This is my digitmap for the line port
(1xx|[34]00xxxx|0800xxxxxxx|1xxxx|[2-9]xxxxxxx|90xx.)
1- Emergency calls
2- Calls to special numbers
3- Toll free calls
4- Calls to providers
5- Local Calls
6- Collect Calls
What I need now is to make this work:
1 - Calls to another state: 0xx xxxxxxx (10 digits) - Call through SP2/FreeVoipDeal, also that first 0 would have to act as "0055".
2 - Calls to US: 001 xxx xxxx - Call through SP1/Google Voice
3 - Calls to any other country: 00xx. go through FreeVoipDeal
4 - Calls to mobile phones: "9xxx xxxx" or "8xxx xxxx" or even "0xx 9xxx xxxx" / "0xx 8xxx xxxx" to those in other states. - Call through SP2/FreeVoipDeal (again adding "0055" instead of "0" and "005584" before 9 or 8 for local calls).
Maybe i would also need some other rules but thats what i can remember now.
I also need to get the FreeVoipDeal callerid and the Automated Assistant working but thats for another topic.
ianobi:
Breno,
Welcome to the forum :)
A lot depends on how your PrimaryLine is set up. The default for OBi110 is:
Physical Interfaces -> PHONE Port -> PrimaryLine : PSTN Line
This means that you do not need to dial **8 to use the PSTN line. I will assume that is the case.
I will have a go at the first part you asked for: 1 - Calls to another state: 0xx xxxxxxx (10 digits) - Call through SP2/FreeVoipDeal, also that first 0 would have to act as "0055". If it makes sense to you, then have a go at the others or come back and I’ll try some more.
Take your existing Line Port DigitMap:
(1xx|[34]00xxxx|0800xxxxxxx|1xxxx|[2-9]xxxxxxx|90xx.)
Change to:
(<0:**20055>x[1-9]xxxxxxx|1xx|[34]00xxxx|0800xxxxxxx|1xxxx|[2-9]xxxxxxx|90xx.)
I made assumptions following very little research – with calls to another state the third digit cannot be a “0”. This means we can avoid conflict with 0800 numbers.
First rule: If a number starts with a 0, the third digit is not a 0 and is ten digits long, then replace the leading 0 with **20055. When this number, **20055xxxxxxxxx, is processed by the Phone Port OutboundCallRoute, the **2 will be removed and 0055xxxxxxxxx will be sent out to Service Provider 2. To make this work a rule 0055xxxxxxxxx will also need to be in the Service Providers -> ITSP Profile B -> General -> DigitMap (which is Msp2).
Simple :D To be fair that is unusually difficult. I hope my assumptions were correct. If not, then I would need more info on Brazilian number formats.
There is a conflict in your original DigitMap as it contains these two rules: 1xx and 1xxxx. If you dial 1xxxx fairly slowly the 1xx rule will match it after 1xx has been dialled. The way we normally deal with this is to change the shortest rule by adding a delay – 1xxS4 – this gives more time for users dialling 1xxxx. The problem is that it delays your emergency number calling. Can any other digits be used to avoid conflicts – maybe the second digits can be different?
Anyhow, that’s more than enough to think about for one post :)
ianobi:
More thoughts about emergency calls! In both of these:
Physical Interfaces -> PHONE Port -> DigitMap
Physical Interfaces -> PHONE Port -> OutboundCallRoute
Replace 911 with 1xx
Then remove 1xx from the Line Port DigitMap.
These changes will remove the conflict and means 1xx calls are sent directly to Line Port with no processing via DigitMaps.
Breno:
Thank you so much :)
I'll try your suggestions as soon as i get home.
Btw the emergency calls are all "19x" here but theres also other public services that goes in the 3 digit category (1xx). Should I leave "19x" at phone port?
Quote from: ianobi on November 19, 2012, 03:47:42 am
More thoughts about emergency calls! In both of these:
Physical Interfaces -> PHONE Port -> DigitMap
Physical Interfaces -> PHONE Port -> OutboundCallRoute
Replace 911 with 1xx
Then remove 1xx from the Line Port DigitMap.
These changes will remove the conflict and means 1xx calls are sent directly to Line Port with no processing via DigitMaps.
ianobi:
I would just go with getting rid of 1xx out of the Line Port DigitMap and letting all three digit numbers starting with 1 be sent direct to the Line Port with no DigitMap involved. This way you can be sure there is minimal delay in sending emergency calls to line. That is why the 911 was not in the Line Port DigitMap to start with (default value for North American emrgency calls).
It does raise an important point about number conflicts - any differences that make a number range unique is very useful when dealing with DigitMaps.
Navigation
[0] Message Index
[#] Next page