Two OBI boxes one Google number.
RonR:
Quote from: Vincent on January 27, 2012, 03:23:25 pm
Result ended in the same thing where call initially rings my obi(home) and after 1-2 rings AA kicks in, I select to continue to call and the obi(work) rings. Very bizarre.
The ONLY way the Auto Attendant will answer an incoming call is if an InboundCallRoute contains an {aa} type rule. I didn't specify any of those, so it must have been the OBiTALK Web Portal putting it/them in.
RonR:
Quote from: Vincent on January 27, 2012, 03:29:44 pm
Quote
Service Providers -> ITSPA -> General -> DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>[2-9]xxxxxx|011xx.|(Mipd)|[^*#]@@.'@'@@.)
where aaa is your local area code.
BTW - does this enable 7 digit dialing or serve some other feature / function? Does it make a difference that I'm testing this configuration on a single /24 network before implementing it into the field? I've tried at the office with both OBI's and now at home with the same results.
Yes, the |<1aaa>[2-9]xxxxxx| rule is for 7-digit dialing.
It shouldn't matter whether the OBi's are on the same or different networks.
RonR:
Quote from: Vincent on January 27, 2012, 04:07:16 pm
So I figured out the issue but don't understand why it was an issue. I have my home google voice number setup to ring my mobile phone in addition to the OBI#1 aforementioned (via google chat). As soon as I disabled my mobile phone from ringing, everything worked perfectly. I then reenabled forwarding to my mobile phone via google voice and everything worked great.
Any ideas?
There had to have been an {aa} type rule in the office OBiTALK Service InboundCallRoute. The incoming call to your house OBi rang the local phone and forked it to the office OBi. After the four second Auto Attendant answer delay, the Auto Attendant answered, cancelling the ringing to your house OBi.
When you decided to remove the OBi's from the OBiTALK Web Portal and configure them manually, did you first reset them to factory defaults to make sure they were starting out clean?
Take a look at the SP2 and LINE Port InboundCallRoute's in both OBi's. They all should be : ph.
Vincent:
Quote from: RonR on January 27, 2012, 05:29:57 pm
Quote from: Vincent on January 27, 2012, 04:07:16 pm
So I figured out the issue but don't understand why it was an issue. I have my home google voice number setup to ring my mobile phone in addition to the OBI#1 aforementioned (via google chat). As soon as I disabled my mobile phone from ringing, everything worked perfectly. I then reenabled forwarding to my mobile phone via google voice and everything worked great.
Any ideas?
There had to have been an {aa} type rule in the office OBiTALK Service InboundCallRoute. The incoming call to your house OBi rang the local phone and forked it to the office OBi. After the four second Auto Attendant answer delay, the Auto Attendant answered, cancelling the ringing to your house OBi.
When you decided to remove the OBi's from the OBiTALK Web Portal and configure them manually, did you first reset them to factory defaults to make sure they were starting out clean?
Take a look at the SP2 and LINE Port InboundCallRoute's in both OBi's. They all should be : ph.
I went through the whole route of resetting to factory configurations and starting from scratch. One other variable that I failed to mention was after having the AA issue, and disabling GV from ringing my mobile phone, I *first* dialed my office GV number which rang on both lines. Following that I dialed my home GV number which then rang on both lines. Following, I readded my mobile phone to my home GV number and everything seemed to continue to work.
This is literally all that change from having AA kicking in to stop kicking in. It doesn't make sense to me at all why the steps above would change AA's behavior.
One question: If I wanted to add additional InboundCallRoute, would the syntax follow the aforementioned; e.g. Code:
{200123456>(<+:>(Msp1)):sp1},{200234567>(<+:>(Msp1)):sp1},{ph}
ditto with X_InboundCallRoute syntax?
Many thanks again for your solution. Hope others find this helpful.
Vincent
RonR:
Quote from: Vincent on January 27, 2012, 05:42:13 pm
One question: If I wanted to add additional InboundCallRoute, would the syntax follow the aforementioned; e.g. Code:
{200123456>(<+:>(Msp1)):sp1},{200234567>(<+:>(Msp1)):sp1},{ph}
ditto with X_InboundCallRoute syntax?
That would work, but this is all that's needed:
{(200123456|200234567)>(<+:>(Msp1)):sp1},{ph}
Navigation
[0] Message Index
[#] Next page
[*] Previous page