Obi110 in United Arab Emirates
RonR:
Another thought...
Are both OBi's running the same version firmware? According to obi-support2, there are interoperability problems between v1.3 and earlier versions in the area of OBiTALK number authentication.
Riyas:
Quote from: RonR on September 17, 2011, 12:09:38 pm
Did you configure this in OBi #1 (the OBI with VG3)?:
Voice Services -> OBiTALK Service -> InboundCallRoute : {200000002>(Mvg3):vg3},{ph}
where 200000002 is the OBiTALK number of OBi #2
Make sure you have the right OBiTALK number for OBi #2 in place of 200000002.
Yes, this part is configured properly.
This is Obi#1 call history :
Call 1 09/17/2011 22:15:46
Terminal ID P2P1 PHONE1
Peer Name Dubai
Peer Number 200996xxx
Direction Inbound Inbound
22:15:46 Ringing
22:15:50 Call Connected
22:16:38 End Call
Quote from: RonR on September 17, 2011, 12:42:03 pm
Another thought...
Are both OBi's running the same version firmware? According to obi-support2, there are interoperability problems between v1.3 and earlier versions in the area of OBiTALK number authentication.
Both software versions are : 1.2.1 (Build: 2384)
RonR:
I assume the InboundCallRoute rules are : {200996xxx>(Mvg3):vg3},{ph}
The problem is this VG3 rule not executing because (1) the OBiTALK number (200996xxx) isn't matching or (2) the passed called number (0177755xxx or 00919xxxxxxxxx) isn't matching the Mvg3 DigitMap.
It appears the correct number is starting out at OBi #2 (2*0177755xxx). OBi #2 should remove the '2*' and send the call to the OBi number stored in Speed Dial 2. 0177755xxx should arrive at OBi #1 from 200996xxx. 200996xxx should match the COT authentication, 0177755xxx should match the Mvg3 DigitMap, and the call should be sent out vg3.
You might try:
{200996xxx:vg3},{ph}
to make sure the OBiTALK number authentication is matching. Assuming the call does not go to the PHONE Port, check the Call History to see what the called number actually was.
Also try:
{200996xxx>(xx.):vg3},{ph}
to see if the problem is with the called number not matching Mvg3. Assuming the call does not go to the PHONE Port, check the Call History to see what the called number actually was.
If all else fails, try:
{vg3},{ph}
Assuming the call does not go to the PHONE Port, check the Call History to see what the called number actually was and where it came from.
RonR:
Another thought...
Try taking the S0's out of the VG3 DigitMap. I wouldn't think those should get in the way, but you never know. They're not part of the InboundCallRoute syntax but I would hope the OBi would ignore them.
Riyas:
Quote from: RonR on September 17, 2011, 01:59:44 pm
You might try:
{200996xxx:vg3},{ph}
{200996xxx>(xx.):vg3},{ph}
Both settings are working for French numbers. :) 0177755xxx is working great. Calls go through with great quality. Thanks for your help.
But I still have one issue. :-[ When I dial an indian number (0091xx.) from Obi#2, I can see in OBI#1 that calls are dialled normally. But it keeps ringing (kind of fake ringing, I've called my relatives in India from my mobile, they told me that they didn't recieve any call). But If I dial this number directly from Obi#1, calls are connected correctly. Settings are same in call history. I don't understand. I am still searching...
Quote from: RonR on September 17, 2011, 02:13:48 pm
Another thought...
Try taking the S0's out of the VG3 DigitMap. I wouldn't think those should get in the way, but you never know. They're not part of the InboundCallRoute syntax but I would hope the OBi would ignore them.
I've removed this S0 but the result is same
Navigation
[0] Message Index
[#] Next page
[*] Previous page