Using OBi Speed Dials w/o Ad Hoc Gateway for 1 stage calling Obi1->Obi2->SP1 sip
limey:
Using the described setup for scenario 2 in ianobi's post http://www.obitalk.com/forum/index.php?topic=6947.msg43848#msg43848, I've got an Obi110 with speedials setup to go via ObiTalk to an Obi100 and then go outbound via sip2sip on SP1.
Using ianobi's examples as a starting point to illustrate, with Obi1 as 500111111 and Obi2 as 200222222 & the Voice Services > OBiTALK Service > InboundCallRoute on Obi2 set to: {500111111>(xx.):sp1},{500111111:aa},{ph}
Speed dial 8 – Sister: pp(ob200222222)
This works fine - call is initiated from Obi1 & gets the AA on Obi2, from where outgoing SP1 calls can be made manually.
Speed dial 10 - Parents: pp(ob200222222*3333)
This fails, producing a 404 Not Found error in Obi1's call history, where the outgoing OBiTALK1 peer number resolves to ob200222222*3333. The call doesn't appear in Obi2's call history, so the call doesn't appear to make it out from Obi1, when *3333 is included on the speeddial. (3333 is a sip2sip test number.)
Any ideas what might be wrong here? I'm suspecting a digimap issue, but ianobi's post didn't mention any further changes been necessary for the 2nd scenario beyond the OBiTALK InboundCallRoute on Obi2.
azrobert:
I don't see anything wrong with your configuration. The 404 error on the OBiTalk network usually means the OBi number wasn't found, but the same OBi number without data was found.
You said in another thread
Quote
Manually upgrading to the current fw build, then updating the GV settings via the ObitTalk portal is the way I will eventually go, but I might try out build 2824 first, just to see if it connects as azrobert reports.
I assume this means you are still on build 2711. Maybe this is a FW problem.
You can try 2 other formats:
Speed Dial 10:
pp(200222222*3333)
The "ob" is optional
or
pp(8*3333)
8 points to speed dial#8
limey:
Quote from: azrobert on July 10, 2015, 09:50:23 pm
I assume this means you are still on build 2711. Maybe this is a FW problem.
You can try 2 other formats:
Speed Dial 10:
pp(200222222*3333)
The "ob" is optional
or
pp(8*3333)
8 points to speed dial#8
pp(200222222*3333) also fails with the 404 error, but...
pp(8*3333) works correctly. ;D
Thanks for that azrobert!
Both Obis are currently still on 2711, so I did consider firmware differences might be at play, but didn't find any reports of such. Still, it's odd that the former fails, but the latter works. Since I wasn't aware of either alternative, I've also learned something.
ianobi:
I thought I would make a few test calls on this one to check that Obihai have not changed how their servers route calls. In my case OBi1 is an OBi110 and OBi2 is an OBi1032 with sip2sip on sp2. Coincidentally, my OBi1032 happens to really be speed dial slot 8.
I set up speed dials and dialled them from the OBi110 using the formats:
pp(ob610222222*3333)
pp(610222222*3333)
pp(8*3333)
All three tests worked fine and resulted in the James Bond theme being received loud and clear. It seems that single stage dialling from one OBi device through another OBi device still works the way it always did.
It seems that we are left with the mystery of why only the pp(8*3333) format works for limey. It seems odd as it must require an extra look-up in the Obihai servers to convert the "8" into the actual number for speed dial slot 8 for the calling device before routing the call. The other formats simply require to be routed by the servers.
limey:
@ianobi - the only things I can think of are that it's related to the 2711 fw build, or that I've somehow introduced something funky into the Obi110 config along the way (I'm fairly conservative about changing stuff, but it remains a possibility).
Whilst pp(8*3333) remains the only variation that currently dials thru to Mr Bond, I must correct myself slightly on the pp(200222222*3333) option - this actually fails with a fast-busy signal rather than a 404 error (sorry - brain fade whilst typing). In the Obi110 log, it reports the outgoing OBiTALK1 peer number resolving to 200222222*3333 & shows a New Call, but gets no further. It doesn't make it as far the receiving Obi100's call log. Maybe a further clue as to what might be happening?
Would pp(8*3333) actually require a server lookup? I thought that the speed-dials were locally stored on the Obi?
Navigation
[0] Message Index
[#] Next page