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

(1/6) > >>

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:
Code:

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.

Navigation

[0] Message Index

[#] Next page