mabbott Posted March 16, 2009 Report Share Posted March 16, 2009 I am trying to send an IM from one extension to another. Both are Polycom's running 2.2.2.0084. When I send an IM one of the phones, it rings the phone for a split second and shows up as a missed call not as an IM. If I send the IM from the pbx, it gets delivered properly to the other phone as an IM. In the logs it looks like the sending phone is trying to call the destination with an invite instead of just sending the message. Is this something that is supported through the pbx? Should I be using a different version of software on the phones other than the version that is listed on the wiki? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 17, 2009 Report Share Posted March 17, 2009 I am trying to send an IM from one extension to another. Both are Polycom's running 2.2.2.0084. When I send an IM one of the phones, it rings the phone for a split second and shows up as a missed call not as an IM. If I send the IM from the pbx, it gets delivered properly to the other phone as an IM. In the logs it looks like the sending phone is trying to call the destination with an invite instead of just sending the message. Is this something that is supported through the pbx? Should I be using a different version of software on the phones other than the version that is listed on the wiki? I would recommend to use the 3.2 version of the Polycom phones. That is much more recent. Do you have the SIP packets that are exchangd between the phones and the PBX? Quote Link to comment Share on other sites More sharing options...
mabbott Posted March 17, 2009 Author Report Share Posted March 17, 2009 I will try out 3.2 as well. INVITE sip:4797@demo.bizfon.com:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.0.0.76;branch=z9hG4bK5138e8d93A80051A From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=CAE127CF-406D3BBE To: <sip:4797@demo.bizfon.com;user=phone> CSeq: 1 INVITE Call-ID: 3cd348eb-71cc9b3d-9137a54c@10.0.0.76 Contact: <sip:4796@10.0.0.76> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER User-Agent: PolycomSoundPointIP-SPIP_501-UA/2.2.2.0084 Supported: 100rel,replaces Allow-Events: talk,hold,conference Max-Forwards: 70 Content-Type: application/sdp Content-Length: 141 v=0 o=- 1167610069 1167610069 IN IP4 10.0.0.76 s=Polycom IP Phone c=IN IP4 10.0.0.76 t=0 0 m=message 5060 sip sip:4796@demo.bizfon.com [9] 2009/03/16 12:15:24: UDP: Opening socket on port 61032 [9] 2009/03/16 12:15:24: UDP: Opening socket on port 61033 [8] 2009/03/16 12:15:24: Using outbound proxy sip:209.190.198.110:59342;transport=udp because UDP packet source did not match the via header [9] 2009/03/16 12:15:24: Resolve 385703: udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: SIP Tx udp:209.190.198.110:59342: SIP/2.0 100 Trying Via: SIP/2.0/UDP 10.0.0.76;branch=z9hG4bK5138e8d93A80051A;rport=59342;received=209.190.198.110 From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=CAE127CF-406D3BBE To: <sip:4797@demo.bizfon.com;user=phone>;tag=f35dc805b0 Call-ID: 3cd348eb-71cc9b3d-9137a54c@10.0.0.76 CSeq: 1 INVITE Content-Length: 0 [9] 2009/03/16 12:15:24: Resolve 385704: udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: SIP Tx udp:209.190.198.110:59342: SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 10.0.0.76;branch=z9hG4bK5138e8d93A80051A;rport=59342;received=209.190.198.110 From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=CAE127CF-406D3BBE To: <sip:4797@demo.bizfon.com;user=phone>;tag=f35dc805b0 Call-ID: 3cd348eb-71cc9b3d-9137a54c@10.0.0.76 CSeq: 1 INVITE User-Agent: Bizfon-PBX/3.2.0.3144 WWW-Authenticate: Digest realm="demo.bizfon.com",nonce="4820c463cc377d4937e0ef2956a6cff2",domain="sip:4797@demo.bizfon.com:5060;user=phone",algorithm=MD5 Content-Length: 0 [9] 2009/03/16 12:15:24: SIP Rx udp:209.190.198.110:59342: ACK sip:4797@demo.bizfon.com:5060 SIP/2.0 Via: SIP/2.0/UDP 10.0.0.76;branch=z9hG4bK5138e8d93A80051A From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=CAE127CF-406D3BBE To: <sip:4797@demo.bizfon.com;user=phone>;tag=f35dc805b0 CSeq: 1 ACK Call-ID: 3cd348eb-71cc9b3d-9137a54c@10.0.0.76 Contact: <sip:4796@10.0.0.76> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER User-Agent: PolycomSoundPointIP-SPIP_501-UA/2.2.2.0084 Max-Forwards: 70 Content-Length: 0 [9] 2009/03/16 12:15:24: SIP Rx udp:209.190.198.110:59342: INVITE sip:4797@demo.bizfon.com:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.0.0.76;branch=z9hG4bKe61636a1759E6B62 From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=CAE127CF-406D3BBE To: <sip:4797@demo.bizfon.com;user=phone> CSeq: 2 INVITE Call-ID: 3cd348eb-71cc9b3d-9137a54c@10.0.0.76 Contact: <sip:4796@10.0.0.76> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER User-Agent: PolycomSoundPointIP-SPIP_501-UA/2.2.2.0084 Supported: 100rel,replaces Allow-Events: talk,hold,conference Authorization: Digest username="4796", realm="demo.bizfon.com", nonce="4820c463cc377d4937e0ef2956a6cff2", uri="sip:4797@demo.bizfon.com:5060;user=phone", response="31a5144e9bca2dd69e3556d64e4831f0", algorithm=MD5 Max-Forwards: 70 Content-Type: application/sdp Content-Length: 141 v=0 o=- 1167610069 1167610069 IN IP4 10.0.0.76 s=Polycom IP Phone c=IN IP4 10.0.0.76 t=0 0 m=message 5060 sip sip:4796@demo.bizfon.com [8] 2009/03/16 12:15:24: Tagging request with existing tag [9] 2009/03/16 12:15:24: Resolve 385705: udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: SIP Tx udp:209.190.198.110:59342: SIP/2.0 100 Trying Via: SIP/2.0/UDP 10.0.0.76;branch=z9hG4bKe61636a1759E6B62;rport=59342;received=209.190.198.110 From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=CAE127CF-406D3BBE To: <sip:4797@demo.bizfon.com;user=phone>;tag=f35dc805b0 Call-ID: 3cd348eb-71cc9b3d-9137a54c@10.0.0.76 CSeq: 2 INVITE Content-Length: 0 [9] 2009/03/16 12:15:24: Using outbound proxy sip:209.190.198.110:59342;transport=udp because of flow-label [9] 2009/03/16 12:15:24: Resolve 385706: url sip:209.190.198.110:59342;transport=udp [9] 2009/03/16 12:15:24: Resolve 385706: a udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: Resolve 385706: udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: UDP: Opening socket on port 53048 [9] 2009/03/16 12:15:24: UDP: Opening socket on port 53049 [9] 2009/03/16 12:15:24: Using outbound proxy sip:209.190.198.110:3022;transport=udp because of flow-label [9] 2009/03/16 12:15:24: Resolve 385707: url sip:209.190.198.110:3022;transport=udp [9] 2009/03/16 12:15:24: Resolve 385707: a udp 209.190.198.110 3022 [9] 2009/03/16 12:15:24: Resolve 385707: udp 209.190.198.110 3022 [9] 2009/03/16 12:15:24: SIP Tx udp:209.190.198.110:3022: INVITE sip:4797@10.0.0.78 SIP/2.0 Via: SIP/2.0/UDP 155.212.72.124:5060;branch=z9hG4bK-d9ca6c8ebf13571188394ea99520b202;rport From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=64758 To: "Demo 4797" <sip:4797@demo.bizfon.com> Call-ID: fdb902a7@pbx CSeq: 15263 INVITE Max-Forwards: 70 Contact: <sip:4797@155.212.72.124:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-PBX/3.2.0.3144 Alert-Info: Internal Call-Info: <http://155.212.72.124/images/extensions61.bmp>;purpose=icon Content-Type: application/sdp Content-Length: 270 v=0 o=- 63632 63632 IN IP4 155.212.72.124 s=- c=IN IP4 155.212.72.124 t=0 0 m=audio 53048 RTP/AVP 0 8 2 3 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2009/03/16 12:15:24: Using outbound proxy sip:209.190.198.110:59342;transport=udp because of flow-label [9] 2009/03/16 12:15:24: Resolve 385708: url sip:209.190.198.110:59342;transport=udp [9] 2009/03/16 12:15:24: Resolve 385708: a udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: Resolve 385708: udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: Resolve 385709: udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: SIP Tx udp:209.190.198.110:59342: SIP/2.0 415 Unsupported Media Type Via: SIP/2.0/UDP 10.0.0.76;branch=z9hG4bKe61636a1759E6B62;rport=59342;received=209.190.198.110 From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=CAE127CF-406D3BBE To: <sip:4797@demo.bizfon.com;user=phone>;tag=f35dc805b0 Call-ID: 3cd348eb-71cc9b3d-9137a54c@10.0.0.76 CSeq: 2 INVITE Contact: <sip:4796@155.212.72.124:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-PBX/3.2.0.3144 Content-Length: 0 [9] 2009/03/16 12:15:24: Resolve 385710: udp 209.190.198.110 3022 [9] 2009/03/16 12:15:24: SIP Tx udp:209.190.198.110:3022: CANCEL sip:4797@10.0.0.78 SIP/2.0 Via: SIP/2.0/UDP 155.212.72.124:5060;branch=z9hG4bK-d9ca6c8ebf13571188394ea99520b202;rport From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=64758 To: "Demo 4797" <sip:4797@demo.bizfon.com> Call-ID: fdb902a7@pbx CSeq: 15263 CANCEL Max-Forwards: 70 Content-Length: 0 [9] 2009/03/16 12:15:24: Using outbound proxy sip:209.190.198.110:59342;transport=udp because of flow-label [9] 2009/03/16 12:15:24: Resolve 385711: url sip:209.190.198.110:59342;transport=udp [9] 2009/03/16 12:15:24: Resolve 385711: a udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: Resolve 385711: udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: Resolve 385712: udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: SIP Tx udp:209.190.198.110:59342: SIP/2.0 487 Request Terminated Via: SIP/2.0/UDP 10.0.0.76;branch=z9hG4bKe61636a1759E6B62;rport=59342;received=209.190.198.110 From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=CAE127CF-406D3BBE To: <sip:4797@demo.bizfon.com;user=phone>;tag=f35dc805b0 Call-ID: 3cd348eb-71cc9b3d-9137a54c@10.0.0.76 CSeq: 2 INVITE Contact: <sip:4796@155.212.72.124:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-PBX/3.2.0.3144 Content-Length: 0 [9] 2009/03/16 12:15:24: Using outbound proxy sip:209.190.198.110:59342;transport=udp because of flow-label [9] 2009/03/16 12:15:24: Resolve 385713: url sip:209.190.198.110:59342;transport=udp [9] 2009/03/16 12:15:24: Resolve 385713: a udp 209.190.198.110 59342 [9] 2009/03/16 12:15:24: Resolve 385713: udp 209.190.198.110 59342 [9] 2009/03/16 12:15:25: SIP Rx udp:209.190.198.110:59342: ACK sip:4797@demo.bizfon.com:5060 SIP/2.0 Via: SIP/2.0/UDP 10.0.0.76;branch=z9hG4bKe61636a1759E6B62 From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=CAE127CF-406D3BBE To: <sip:4797@demo.bizfon.com;user=phone>;tag=f35dc805b0 CSeq: 2 ACK Call-ID: 3cd348eb-71cc9b3d-9137a54c@10.0.0.76 Contact: <sip:4796@10.0.0.76> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER User-Agent: PolycomSoundPointIP-SPIP_501-UA/2.2.2.0084 Authorization: Digest username="4796", realm="demo.bizfon.com", nonce="4820c463cc377d4937e0ef2956a6cff2", uri="sip:4797@demo.bizfon.com:5060;user=phone", response="31a5144e9bca2dd69e3556d64e4831f0", algorithm=MD5 Max-Forwards: 70 Content-Length: 0 [7] 2009/03/16 12:15:25: Other Ports: 1 [7] 2009/03/16 12:15:25: Call Port: fdb902a7@pbx#64758 [9] 2009/03/16 12:15:25: SIP Rx udp:209.190.198.110:3022: SIP/2.0 100 Trying Via: SIP/2.0/UDP 155.212.72.124:5060;branch=z9hG4bK-d9ca6c8ebf13571188394ea99520b202;rport From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=64758 To: "Demo 4797" <sip:4797@demo.bizfon.com>;tag=EC675947-418DD4FA CSeq: 15263 INVITE Call-ID: fdb902a7@pbx Contact: <sip:4797@10.0.0.78> User-Agent: PolycomSoundPointIP-SPIP_501-UA/2.2.2.0084 Content-Length: 0 [9] 2009/03/16 12:15:25: SIP Rx udp:209.190.198.110:59342: ACK sip:4797@demo.bizfon.com:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.0.0.76;branch=z9hG4bKe61636a1759E6B62 From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=CAE127CF-406D3BBE To: <sip:4797@demo.bizfon.com;user=phone>;tag=f35dc805b0 CSeq: 2 ACK Call-ID: 3cd348eb-71cc9b3d-9137a54c@10.0.0.76 Contact: <sip:4796@10.0.0.76> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER User-Agent: PolycomSoundPointIP-SPIP_501-UA/2.2.2.0084 Authorization: Digest username="4796", realm="demo.bizfon.com", nonce="4820c463cc377d4937e0ef2956a6cff2", uri="sip:4797@demo.bizfon.com:5060;user=phone", response="7a9958a0b0706fe76428a1d18119b39c", algorithm=MD5 Max-Forwards: 70 Content-Length: 0 [9] 2009/03/16 12:15:25: Message repetition, packet dropped [9] 2009/03/16 12:15:25: SIP Rx udp:209.190.198.110:3022: SIP/2.0 200 OK Via: SIP/2.0/UDP 155.212.72.124:5060;branch=z9hG4bK-d9ca6c8ebf13571188394ea99520b202;rport From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=64758 To: "Demo 4797" <sip:4797@demo.bizfon.com> CSeq: 15263 CANCEL Call-ID: fdb902a7@pbx Contact: <sip:4797@10.0.0.78> User-Agent: PolycomSoundPointIP-SPIP_501-UA/2.2.2.0084 Content-Length: 0 [7] 2009/03/16 12:15:25: Call fdb902a7@pbx#64758: Clear last request [9] 2009/03/16 12:15:25: SIP Rx udp:209.190.198.110:3022: SIP/2.0 487 Request Cancelled Via: SIP/2.0/UDP 155.212.72.124:5060;branch=z9hG4bK-d9ca6c8ebf13571188394ea99520b202;rport From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=64758 To: "Demo 4797" <sip:4797@demo.bizfon.com>;tag=EC675947-418DD4FA CSeq: 15263 INVITE Call-ID: fdb902a7@pbx Contact: <sip:4797@10.0.0.78> User-Agent: PolycomSoundPointIP-SPIP_501-UA/2.2.2.0084 Content-Length: 0 [7] 2009/03/16 12:15:25: Call fdb902a7@pbx#64758: Clear last INVITE [9] 2009/03/16 12:15:25: Resolve 385714: url sip:209.190.198.110:3022;transport=udp [9] 2009/03/16 12:15:25: Resolve 385714: a udp 209.190.198.110 3022 [9] 2009/03/16 12:15:25: Resolve 385714: udp 209.190.198.110 3022 [9] 2009/03/16 12:15:25: SIP Tx udp:209.190.198.110:3022: ACK sip:4797@10.0.0.78 SIP/2.0 Via: SIP/2.0/UDP 155.212.72.124:5060;branch=z9hG4bK-d9ca6c8ebf13571188394ea99520b202;rport From: "Demo 4796" <sip:4796@demo.bizfon.com>;tag=64758 To: "Demo 4797" <sip:4797@demo.bizfon.com>;tag=EC675947-418DD4FA Call-ID: fdb902a7@pbx CSeq: 15263 ACK Max-Forwards: 70 Contact: <sip:4797@155.212.72.124:5060;transport=udp> Content-Length: 0 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 17, 2009 Report Share Posted March 17, 2009 I will try out 3.2 as well. [...] m=message 5060 sip sip:4796@demo.bizfon.com Interesting concept to send the message in the SDP... Though in the meantime people would probably use the MESSAGE method (SIMPLE) or even better XMPP. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.