Connecting Panasonic IP phone KX-TGP600 with Obi202- in Proxy

Started by Krish-VA, June 19, 2018, 03:37:30 AM

Previous topic - Next topic

Krish-VA

I like to connect my  Panasonic IP phone  KX-TGP600 to Obi202. I followed all the avilable methods in the web.

The inbound call rings. But outbound Calls not going and getting busy signal.
I followed the prcedure laid out in the link:

https://www.ukvoipforums.com/viewtopic.php?t=229

If anyone connected Panasonic IP phone  KX-TGP600 to Obi202, Please help me.


lrosenman

I have the opposite problem.  I can get the panasonic to call out, but can't set the Obi to ring the Panasonic.

Can we compare configs?

What do your EXACT OBI and Panasonic configs look like?


lrosenman

Ok, I'm now in the same state as @Krish-VA.

I get the following from the Obi's SIP Debug:

Jul  1 13:54:15 192.168.200.109  INVITE sip:7373463291@192.168.200.109:5062 SIP/2.0^M Max-Breadth: 60^M Via: SIP/2.0/UDP 192.168.200.94:5060;branch=z9hG4bK54698ec8^M Max-Forwards: 70^M Call-ID: 6b2a28bc-5748c522cefe8e05f19f0080f0808080@KX-TGP600(M)^M From: "GV-LER" <sip:1001@192.168.200.109>;tag=1832587521^M To: <sip:7373463291@192.168.200.109>^M CSeq: 1 INVITE^M Allow: INVITE,ACK,CANCEL,BYE,PRACK,INFO,UPDATE,OPTIONS,MESSAGE,NOTIFY,REFER^M Supported: 100rel,replaces,early-session^M Content-Disposition: session^M Contact: <sip:1001@192.168.200.94:5060>^M Content-Type: application/sdp^M User-Agent: Panasonic-KX-TGP600/06.001 (080023ce37c3)^M Content-Length: 268^M ^M v=0^M o=- 1530471255 1530471255 IN IP4 192.168.200.94^M s=-^M c=IN IP4 192.168.200.94^M t=0 0^M m=audio 16946 RTP/AVP 8 18 0 101^M a=rtpmap:8 PCMA/8000^M a=rtpmap:18 G729/8000^M a=rtpmap:0 PCMU/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-15^M a=sendrecv^M a=ptime:20^M
Jul  1 13:54:15 192.168.200.109  sendto c0a8c85e:5060(495)
Jul  1 13:54:15 192.168.200.109  SIP/2.0 401 Unauthorized^M Call-ID: 6b2a28bc-5748c522cefe8e05f19f0080f0808080@KX-TGP600(M)^M CSeq: 1 INVITE^M Content-Length: 0^M From: "GV-LER" <sip:1001@192.168.200.109>;tag=1832587521^M To: <sip:7373463291@192.168.200.109>^M Via: SIP/2.0/UDP 192.168.200.94:5060;branch=z9hG4bK54698ec8;received=192.168.200.94;rport=5060^M WWW-Authenticate: Digest algorithm=MD5,nonce="f1f63f0eEF9F8ACF",opaque="7f7eb15af67e67b2",realm="pnn.obihai.com",nonce="5F7F17BE",response="5F7F17BE5F7F17BE5F7F17BE5F7F17BE"^M ^M
Jul  1 13:54:15 192.168.200.109  RxFrom:c0a8c85e:5060
Jul  1 13:54:15 192.168.200.109  ACK sip:7373463291@192.168.200.109:5062 SIP/2.0^M Via: SIP/2.0/UDP 192.168.200.94:5060;branch=z9hG4bK54698ec8^M Max-Forwards: 70^M Call-ID: 6b2a28bc-5748c522cefe8e05f19f0080f0808080@KX-TGP600(M)^M From: "GV-LER" <sip:1001@192.168.200.109>;tag=1832587521^M To: <sip:7373463291@192.168.200.109>^M CSeq: 1 ACK^M User-Agent: Panasonic-KX-TGP600/06.001 (080023ce37c3)^M Content-Length: 0^M ^M
Jul  1 13:54:15 192.168.200.109  RxFrom:c0a8c85e:5060
Jul  1 13:54:15 192.168.200.109  INVITE sip:7373463291@192.168.200.109:5062 SIP/2.0^M Max-Breadth: 60^M Via: SIP/2.0/UDP 192.168.200.94:5060;branch=z9hG4bK5e81e7f9^M Max-Forwards: 70^M Call-ID: 6b2a28bc-5748c522cefe8e05f19f0080f0808080@KX-TGP600(M)^M From: "GV-LER" <sip:1001@192.168.200.109>;tag=1832587521^M To: <sip:7373463291@192.168.200.109>^M CSeq: 2 INVITE^M Authorization: Digest realm="pnn.obihai.com",nonce="5F7F17BE",opaque="7f7eb15af67e67b2",algorithm=MD5,uri="sip:7373463291@192.168.200.109:5062",username="1001",response="6e71f1ed18c8814c362f0a53e635540d"^M Allow: INVITE,ACK,CANCEL,BYE,PRACK,INFO,UPDATE,OPTIONS,MESSAGE,NOTIFY,REFER^M Supported: 100rel,replaces,early-session^M Content-Disposition: session^M Contact: <sip:1001@192.168.200.94:5060>^M Content-Type: application/sdp^M User-Agent: Panasonic-KX-TGP600/06.001 (080023ce37c3)^M Content-Length: 268^M ^M v=0^M o=- 1530471255 1530471255 IN IP4 192.168.200.94^M s=-^M c=IN IP4 192.168.200.94^M t=0 0^M m=audio 16946 RTP/AVP 8 18 0 101^M a=rtpmap:8 PCMA/8000^M a=rtpmap:18 G729/8000^M a=rtpmap:0 PCMU/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-15^M a=sendrecv^M a=ptime:20^M
Jul  1 13:54:15 192.168.200.109  sendto c0a8c85e:5060(495)
Jul  1 13:54:15 192.168.200.109  SIP/2.0 401 Unauthorized^M Call-ID: 6b2a28bc-5748c522cefe8e05f19f0080f0808080@KX-TGP600(M)^M CSeq: 2 INVITE^M Content-Length: 0^M From: "GV-LER" <sip:1001@192.168.200.109>;tag=1832587521^M To: <sip:7373463291@192.168.200.109>^M Via: SIP/2.0/UDP 192.168.200.94:5060;branch=z9hG4bK5e81e7f9;received=192.168.200.94;rport=5060^M WWW-Authenticate: Digest algorithm=MD5,nonce="f1f63f0eEF9F8ACF",opaque="7f7eb15af67e67b2",realm="pnn.obihai.com",nonce="6DFE0433",response="6DFE04336DFE04336DFE04336DFE0433"^M ^M
Jul  1 13:54:15 192.168.200.109  RxFrom:c0a8c85e:5060
Jul  1 13:54:15 192.168.200.109  ACK sip:7373463291@192.168.200.109:5062 SIP/2.0^M Via: SIP/2.0/UDP 192.168.200.94:5060;branch=z9hG4bK5e81e7f9^M Max-Forwards: 70^M Call-ID: 6b2a28bc-5748c522cefe8e05f19f0080f0808080@KX-TGP600(M)^M From: "GV-LER" <sip:1001@192.168.200.109>;tag=1832587521^M To: <sip:7373463291@192.168.200.109>^M Authorization: Digest realm="pnn.obihai.com",nonce="5F7F17BE",opaque="7f7eb15af67e67b2",algorithm=MD5,uri="sip:7373463291@192.168.200.109:5062",username="1001",response="6e71f1ed18c8814c362f0a53e635540d"^M CSeq: 2 ACK^M User-Agent: Panasonic-KX-TGP600/06.001 (080023ce37c3)^M Content-Length: 0^M ^M


Panasonic IP: 192.168.200.94
ObiHai IP: 192.168.200.109


Panasonic Line config
ObiHai ITSP config
ObiHai SP config

@SteveInWa Any ideas here?

drgeoff

The latest firmware for OBi200/202 has broken the ability for SIP phones to register to it.

Can your phone make a call if not SIP registered?

azrobert has a post somwhere about this and a possible workaround.

lrosenman

Not sure, it's sending the INVITE and the Obi200 is sending 401.

You can see my options on the Panasonic line config link in my post.



lrosenman

If anyone else wants help with ObiHai and Panasonic KX-TGP600, feel free to ping me.

Krish-VA

I am still having problem in connecting Panasonic KX-TPG600 to OBI202.  I am not able to ping lrosenman for help.

lrosenman

Krish-VA and I have been in touch.  He looks to be downlevel on the Panasonic firmware.

For others, the current fw is:
https://panasonic.net/cns/pcc/support/sipphone/download/TGP6/na.html


lrosenman

We got it all working.  The last issue was the Panasonic defaulting to a line not set up for outbound.


jholme004

Hi,
  I was reading this post and was wondering if anyone could help me out. For the life of me, I can't get this to work. This is my first time using the TGP600, so I am wondering if it is an issue on that side...(I've gotten the Obi devices to work with Asterisk, 3CX and SIP to one another).

I used the screen shots above  as a guide and have it matched almost exactly - except for using my local information. It seems if I have X_RegisterEnable=YES, I get a 401 error at the Obi. If I uncheck it, the TGP shows Registration failure by no response and there is no log enrty from the Obi.

OBI IP: 172.16.3.6
TGP IP: 172.16.1.103
(Large IP Range; All on same Subnet)

Any thoughts? 
-Jason

vtsnaab

I have the Panasonic KX-TGP500 and never thought to connect it with the Obi box, interesting.
After using it for a few months it needed new batteries, so now it is just hanging around & I use Android for my SIP number instead.
My conclusion is that the Panasonic SIP phone is a tinkerer's best friend vs. Android SIP which is loads easier to deal with.

jholme004

I went into System settings and Enabled Multi Number, SIP Trunking Service, and Non_Registering SIP UA. The TGP now shows the line as "Registered" with the Obi, but when I attempt to make a call the logs show "[SIP(L1)]Registration failure by no response".

Anyone with a TGP-6oo working that can help with this config?
-Jason

jholme004

Put this off for a while...added an Asterisk box between the two and now want to simplify...

So I followed @Irosenman's screenshots as a guide.  I can call outbound and hear the other side ring. The other side receives the call with the proper Caller ID. When the other side answers, the call drops and on my side I get fast busies. This happens when calling from the TGP using GoogleVoice or wither of the phone ports. I've confirmed, all CODECS are  U-Law. I don't have a SIP ALG setting in the router (Using the Comcast Special), but I can say my Asterisk box has no issues. I am convinced this has to be a setting, because all calls from Asterisk to GoogleVoice, BulkVS, or Phone Ports (all via Obi) work with no issues.

Here are my settings:
TGP600: 10.16.3.103; Firmware v13.102
     Enable Multi Number = Yes
     Enable SIP Trunk Service = Yes
     Enable Non-registering SIP UA = Yes

Obi202:  10.16.3.7; Firmware v3.2.2 (Build: 8680EX)

Any thoughts?

-Jason

lrosenman

I think the non-registering UA is the magic.  The 202 seems(!) to not like to play registration correctly now for a long time.

jholme004

I do already have that selected.

The 202 seems to be doing what it should - its allowing the TGP to place calls, but as soon as the call is answered, the TGP disconnects.  The TGP does not do this connected to asterisk.
-Jason

lrosenman

I need to pull my full config for you.  Mine works.

Let me try to do that this weekend.

lrosenman

Here's an export of my operational values from the maintenance page.  Maybe you can compare yours to mine?

jholme004

Thank you...
My config file (on the server) is no where near this big...I'll start sifting through.

How did you export this from the TGP? I can't seem to find an option to do that. (Or is this your config the TGP downloads?)
-Jason