Using OBi Speed Dials w/o Ad Hoc Gateway for 1 stage calling Obi1->Obi2->SP1 sip
limey:
Quote from: azrobert on July 13, 2015, 06:13:08 am
It's working correctly.
Any call from OBi1 using OBiTalk will have a CallerID=500111111
If the call is sent to OBi2 phone port, the original CallerID will magically be passed.
Could have sworn it wasn't getting the AA before, but it's possible I missed the effects after making changes.
Quote
Did you upgrade FW?
Not yet - making sure I know where I am with the current config first.
Quote
Try this:
OBi1 Line inbound route
ph,pp(200222222*0),pp(290xxxxxx)
What does the *0 part of the Obi1 Line inbound route do?
Quote
OBi2 OBiTalk inbound route
{500111111>0:ph},{500111111>(xx.):sp1},{500111111:aa},{ph}
Same question for >0 for the Obi2's OBiTalk inbound route?
azrobert:
I assumed you have a speed dial defined as pp(200222222) and want it routed to the AA. This call will not have any data, so it will not match rule {500111111>(xx.):sp1}. Rule {500111111:aa} will match it because it's only checking for the OBi number and will send the call to the AA.
*0 will pass zero as data, the same as *3333 will pass 3333 as data. You can use any character string as long as it's unique.
{500111111>0:ph} will check for zero and upon a match will send the call to the phone port.
limey:
Quote from: azrobert on July 14, 2015, 06:12:45 am
I assumed you have a speed dial defined as pp(200222222) and want it routed to the AA. This call will not have any data, so it will not match rule {500111111>(xx.):sp1}. Rule {500111111:aa} will match it because it's only checking for the OBi number and will send the call to the AA.
*0 will pass zero as data, the same as *3333 will pass 3333 as data. You can use any character string as long as it's unique.
{500111111>0:ph} will check for zero and upon a match will send the call to the phone port.
That's quite clever, if I understand it right...
So, all incoming calls to Obi1's Line port, get 0 tacked on as data & are then forked to Obi2 via ObiTALK.
Then, the {500111111>0:ph} in Obi2's ObiTALK inbound route matches that 0 data & hands that call to it's Phone port, with order precedence preventing any matches from the remaining sp1/aa/ph parts of the ObiTALK inbound route.
As long as the value tacked on as data never corresponds to anything that you'd ever want to call on the default outbound Obi2 port via single stage dialing, then all is good.
Nifty.
[Edit: Just tried your suggestions & they seem to do the trick - thanks.]
Hadi:
I have an another problem. I can not even connect to obi2 from obi1. I have two OBi110s at FW2824 and obi1 can connect to obi2 just 1 second ( I just hear welcome to) and then disconnected. When I call Obi2 from Obion, I don't have any problem. Can you solve my problem too?
on obi2:
OBi2 OBiTalk inbound route:
{(290xxxxxx|200xxxxxx):AA}
azrobert:
This sounds like a network problem. Check the local and remote routers for SIP ALG. If it's enabled, disable it. Some routers don't have this option.
The following has nothing to do with your problem.
In Voice Services -> Auto Attendant
Set these parms
Welcome: &pause()
MenuTitle: &pause()
Now you don't hear these prompts when routed to the AA
Navigation
[0] Message Index
[#] Next page
[*] Previous page