News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

OBI202 with Yate server for CNAM, is not working...

Started by sjmyst, December 13, 2014, 04:16:23 AM

Previous topic - Next topic

sjmyst

Hi,

I'm trying to get CNAM (Caller Name) working for my OBI202 using a procedure documented by Kevin here:

http://blog.paulisse.com/2014/09/custom-caller-id-names-with-google.html

I've set up a VMWare Player system installed with Ubuntu 12.04.05.  It is running on an HTPC (fancy name for the Windows 7 PC that is connected to my TV in my den).

I am able to see that the OBI202 is sending SIP msgs to/from the Yate server using tshark.  The first message is refused indicating "Unauthorized", but I see a 2nd message almost immediately that seems to succeed in Registering the Yate server  (my OBI202 is 192.168.1.117, the Yate server is 192.168.1.125):

207971   2014-12-13 05:47:24.990689000   192.168.1.117   192.168.1.125   SIP   788   Request: REGISTER sip:192.168.1.125:5060 |
207972   2014-12-13 05:47:25.000826000   192.168.1.125   192.168.1.117   SIP   351   Status: 100 Trying    (0 bindings) |
207973   2014-12-13 05:47:25.006860000   192.168.1.125   192.168.1.117   SIP   541   Status: 401 Unauthorized    (0 bindings) |
207974   2014-12-13 05:47:25.031206000   192.168.1.117   192.168.1.125   SIP   788   Request: REGISTER sip:192.168.1.125:5060 |
207975   2014-12-13 05:47:25.040031000   192.168.1.125   192.168.1.117   SIP   351   Status: 100 Trying    (0 bindings) |
207976   2014-12-13 05:47:25.045497000   192.168.1.125   192.168.1.117   SIP   497   Status: 200 OK    (1 bindings) |

I can see on the OBI202 that the Yate Server is showing as registered on my SP4 on the OBI202 "System Status" screen:

SP4 Service Status
Parameter Name   Value
Status   Registered (server=192.168.1.125:5060; expire in 39s)

The "expire" value changes as I refresh.  And, the SIP sequence above reoccurs every 60 seconds in tshark.  I'm not sure why the first attempt is given "unauthorized".  I do know if I just change the configuration on the Yate side, changing only the password, that instead of 1 failure followed by 1 success (like above), that I see 3 "authorization" failure messages.  So, not sure why the first failure.  But, on the 2nd attempt the registration seems to complete.

In the Google Voice SP1 configuration I am pointing my Google Voice to the Yate Server using the X_InboundCallRoute field in SP1 on the OBI202 config screen on the OBI like described in Kevin's instructions (I've changed my phone and password below to protect the innocent).  I've tried the value below both with and without surrounding braces "{}":

sp4(1234567890/$1@192.168.1.125;ui=obi202user:workingpassword)

After I "submit" and reboot the OBI202, I can refresh and see the configuration still there for this X_InboundCallRoute field in SP1 that is supposed to be forwarding the call from the SP1 GV to the Yate Server.  But, when I make a call, that field reverts back to the value that DOESN'T forward the call to the Yate Server:

{ph1,ph2}

The change back occurs when I try to make a phone call that "should" try to use the Yate server.  So, when I refresh that page on my OBI202's web page, I can see the value I set it to above that is supposed to forward to the Yate server (the 1st value with my phone number and the SP4 stuff).  I make the call.  Refresh again, and the X_InboundCallRoute value changes back to the GV value.  Also, I have tshark running on my PC where the VMWare and the Yate server is running, and I don't see any messages being attempted from the OBI202 to the Yate server when the call is attempted.  The Yate log also doesn't show anything.

Any ideas what I might be doing wrong that is causing the OBI202 to not even attempt to forward the call to the Yate server and to revert the X_InboundCallRoute field back to it's "GV" value?

The OBI202 is updated with the latest firmware.  I am able to ping from the Yate server VMWare to the OBI202 successfully.  The tshark seems to show that communications are fine (with the anomaly of the first "unauthorized" response).  I think I've followed the instructions on Kevin's web site (part 1 and part 2) to have Yate up and running and configured to register and receive the call.  I haven't installed Kevin's perl script yet.  So, I'm really at "part 2" where the OBI202 is supposed to just forward the call to the Yate server, and the Yate server is supposed to give it back to the OBI202 (SP1->SP4->SP1) and the call completes (no CNAM yet).  When the call is attempted, it does complete and I am able to pick up and talk on that call.  It just isn't going through the Yate server like it's supposed to.

Any ideas?

Thanks in advance for any help anyone can provide.

Regards,
sjmyst

azrobert

If you use the local interface to configure your OBi you must disable OBiTalk auto provisioning, otherwise OBiTalk will overlay any changes you make.

System Management -> Auto Provisioning
Under OBiTalk Provisioning
Method: Disabled

sjmyst

Perfect!

I was thinking it was going to be something a lot more complicated.

I'm now seeing the SIP messages to the Yate and back when a call is made.  Onward to CNAM!!

Thanks again!

Regards,
sjmyst

azrobert

#3
Asterisk has the same feature, but it's already built in. All you have to do is turn on the Superfecta service. You can also use the phone book for cname and set which method has priority.

Here are the virtual machine downloads:
http://pbxinaflash.com/vm/

See: http://www.obitalk.com/forum/index.php?topic=5615.0