Setting up Obi110 for Brazil PSTN + GVoice + SIP
Breno:
This is my current dial plan and it seems to be working great so far:
(<0:**20055>x[1-9]xxxxxxxx|[34]00xxxx|0800xxxxxxx|1xxxx|[2-7]xxxxxxx|<8:**20055848>xxxxxxx|<9:**20055849>xxxxxxx|90xx.|<001:**1>[2-9]xx[2-9]xxxxxx|<00:**200>xx.)
1 - Calls to other states (SP2)
2 - Calls to special numbers (PSTN)
3 - Calls to toll free (PSTN)
4 - Calls to providers customer service (PSTN)
5 - Calls to local landlines (PSTN)
6 - Calls to local mobiles starting with 8 (SP2)
7 - Calls to local mobiles starting with 9 (SP2)
8 - Collect calls (PSTN)
9 - Calls to US (SP1)
10 - Calls to other countries (SP2)
Could I simplify this digitmap? Or should I change anything else?
As for the SP2 callerid it appears to work fine when i call to landlines (my pstn number shows up in the phone of the person im calling) but when i call to a mobile phone it shows up an access number from rio de janeiro. Does anyone that use betamax has any experience on this?
I have disabled all the obitalk features and im using only the local configuration page right now (had to do everything from scratch) obitalk was giving me lots of red exclamation marks and conflicting with the local configuration.
I used this page to configure Google Voice - http://www.obihai.com/itspConfiguration/itspConfiguration-googlevoice.html
And for the SP2 provider i did it manually.
Now about the auto attendent feature how does it work? How do I configure it without obitalk? Can it be used while the phone is making or receiving PSTN calls? Does it work through the ObiON iphone app (connecting through internet instead of call back)?
ianobi:
You certainly got your head around digit maps quickly :)
I'm not sure about this rule:
<001:**1>[2-9]xx[2-9]xxxxxx
It probably needs to be:
<001:**11>[2-9]xx[2-9]xxxxxx
to give the leading 1 and eleven digits that GV needs.
The red exclamation marks are not a problem, they just show that you have changed a setting and that you are in control of that setting.
The aa settings are simply a matter of changing InboundCallRoutes to include rules such as {(12345678912):aa},{ph} where 12345678912 is a Caller ID to which you wish to give access to the aa.
Have a read about aa here in forum and in OBiDeviceAdminGuide and I will be back tomorrow - or many helpful people nearer your time zone may be here any minute now :)
Breno:
Here is my current line port digitmap:
(<0:**20055>x[1-9]xxxxxxxx|0800xxxxxxx|10xxx|105x|[2-4]xxxxxxx|<8:**20055848>xxxxxxx|<9:**20055849>xxxxxxx|90xx.|<001:**1>[2-9]xx[2-9]xxxxxx|<00:**200>xx.)
I removed the rule for special numbers (starting with 300 and 400) because it would conflict with regular numbers so its covers everything on [2-4]xxxxxxx. Added "105x" that is also used for some mobile providers customer service.
ianobi:
Brazil must be the most challenging country in the world to design a DigitMap for :)
I was wrong in my previous comments concerning <001:**1>[2-9]xx[2-9]xxxxxx The rule works because of Msp1:
Service Providers -> ITSP Profile A -> General -> DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|(Mipd)|[^*]@@.'@'@@.)
This is where the leading 1 gets added: <1>[2-9]xxxxxxxxx
I would remove 011xx.|(Mipd)|[^*#]@@. The 011xx. is not wanted and I don’t believe GV allow sip uri dialling (anything@anywhere) format which is what the other rules are for. Always be wary of this rule [^*#]@@. As far as digits are concerned it is the same as xx.
There is a possible conflict here |10xxx|105x| If someone dialled 105xx quite slowly it could be matched by 105x The normal way to avoid this is by adding a delay to the shorter rule like so:
|10xxx|105xS4| This gives a user up to four seconds to dial the last digit in the first rule before the second rule matches it.
The Auto Attendant can be used in various ways, but to get to the aa the Caller ID must be in a rule in an InboundCallRoute e.g:
Line Port InboundCallRoute {(12345678912):aa},{ph} where 12345678912 is a Caller ID to which you wish to give access to the aa. Change the rule to {(12345678912):aa($1)},{ph}, then if you clear down before aa answers, aa will call you back and offer its service to you.
To use aa from OBiON a rule like this is needed:
OBiTALK Service > InboundCallRoute > {(290123456):aa},{ph} where 290123456 is your OBioN softphone number.
QBZappy:
Quote from: ianobi on November 21, 2012, 09:06:01 am
... then if you clear down before aa answers, ...
"clear down" you Brits talk funny!!! Learn to speak Canadian. (hang up) :D
Navigation
[0] Message Index
[#] Next page
[*] Previous page