• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
HP Recommended

Hello,

 

 

I am experiecing an issue with FreeSWITCH (FreeSWITCH Version 1.4.12+git~20141023T150634Z~11aa88a8b7~64bit (git 11aa88a 2014-10-23 15:06:34Z 64bit) where NOTIFY packets are ocassionally being rejected with a 500 Internal Server Error by both a VVX 400 running 4.1.6.4835 as well as a SoundPoint IP 550 running 4.0.4.2906.  Both of these cases were unrelated to each other but share the same symptoms.  The NOTIFY packets are in the dialogue created by a line-sieze SUBSCRIBE for SCA updates to the phone.  I have not been able to track down the exact call scenario where this issue is a problem.  I am aware that there are several changes made to FreeSWITCH as of 1.4.15 regarding NOTIFYs, but the bug in question (https://freeswitch.org/jira/browse/FS-7100) states that only one NOTIFY was being send to one of the shared endpoints as oppose to all endpoints that were SUBSCRIBEd to that line in the first place.  

 

My question for the community is: Has anyone else has seen an issue similiar to this where the phones themselves are rejecting the NOTIFY in this fashion?  Was the issue properly fixed in 1.4.15?  Symtoms for this call include the inability to seize the line to make a call (i.e.  the line button doesnt respond after pressing it).  Here is a trace of one dialogue where the user attempted to seize the shared line to make the call outbound but the phone responded with a 500 after the NOTIFY was sent to it. The other endpoint sharing the line (2044) is also a Polycom IP 550 running the same version of the firmware.

 

recv 648 bytes from tcp/[10.26.153.74]:45349 at 13:48:47.191489:
------------------------------------------------------------------------
SUBSCRIBE sip:2044@10.66.30.20:5065;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.26.153.74:24334;branch=z9hG4bKf70f2efe5F51065F
From: "polycom 550" <sip:2044@10.66.30.20:5065>;tag=22064DE4-BCE24995
To: <sip:2044@10.66.30.20:5065>
CSeq: 1 SUBSCRIBE
Call-ID: d6f865f8-943b8209-fbabcd2@10.26.153.74
Contact: <sip:2044@10.26.153.74:24334;transport=tcp>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
Event: line-seize
Call-Info: <sip:10.66.30.20>;appearance-index=1
User-Agent: PolycomSoundPointIP-SPIP_550-UA/4.0.4.2906
Accept-Language: en
Max-Forwards: 70
Expires: 30
Content-Length: 0

------------------------------------------------------------------------
send 752 bytes to tcp/[10.26.153.74]:45349 at 13:48:47.236146:
------------------------------------------------------------------------
SIP/2.0 202 Accepted
Via: SIP/2.0/TCP 10.26.153.74:24334;branch=z9hG4bKf70f2efe5F51065F;rport=45349
From: "polycom 550" <sip:2044@10.66.30.20:5065>;tag=22064DE4-BCE24995
To: <sip:2044@10.66.30.20:5065>;tag=YIyjbbFm5Lol
Call-ID: d6f865f8-943b8209-fbabcd2@10.26.153.74
CSeq: 1 SUBSCRIBE
Contact: <sip:2044@10.66.30.20:5065;transport=tcp>
Expires: 30
User-Agent: Freeswitch
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Subscription-State: active;expires=30
Content-Length: 0

------------------------------------------------------------------------
send 861 bytes to tcp/[10.26.153.74]:24334 at 13:48:47.236343:
------------------------------------------------------------------------
NOTIFY sip:2044@10.26.153.74:24334;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.66.30.20:5065;branch=z9hG4bKFUS1KBjF330HF
Max-Forwards: 70
From: <sip:2044@10.66.30.20:5065>;tag=YIyjbbFm5Lol
To: "polycom 550" <sip:2044@10.66.30.20:5065>;tag=22064DE4-BCE24995
Call-ID: d6f865f8-943b8209-fbabcd2@10.26.153.74
CSeq: 70213599 NOTIFY
Contact: <sip:2044@10.66.30.20:5065;transport=tcp>
Expires: 30
Call-Info: <sip:10.66.30.20>;appearance-index=1
User-Agent: Freeswitch
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Event: line-seize
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Subscription-State: active;expires=30
Content-Length: 0

------------------------------------------------------------------------
send 870 bytes to tcp/[10.26.153.74]:24334 at 13:48:47.241588:
------------------------------------------------------------------------
NOTIFY sip:2044@10.26.153.74:24334;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.66.30.20:5065;branch=z9hG4bKjp5BSv4Sty39H
Max-Forwards: 70
From: <sip:2044@10.66.30.20:5065>;tag=YIyjbbFm5Lol
To: "polycom 550" <sip:2044@10.66.30.20:5065>;tag=22064DE4-BCE24995
Call-ID: d6f865f8-943b8209-fbabcd2@10.26.153.74
CSeq: 50006353 NOTIFY
Contact: <sip:2044@10.66.30.20:5065;transport=tcp>
Call-Info: <sip:10.66.30.20>;appearance-index=*;appearance-state=idle
User-Agent: Freeswitch
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Event: line-seize
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Subscription-State: active;expires=30
Content-Length: 0

------------------------------------------------------------------------
recv 492 bytes from tcp/[10.26.153.74]:24334 at 13:48:47.247259:
------------------------------------------------------------------------
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.66.30.20:5065;branch=z9hG4bKFUS1KBjF330HF
From: <sip:2044@10.66.30.20:5065>;tag=YIyjbbFm5Lol
To: "polycom 550" <sip:2044@10.66.30.20:5065>;tag=22064DE4-BCE24995
CSeq: 70213599 NOTIFY
Call-ID: d6f865f8-943b8209-fbabcd2@10.26.153.74
Contact: <sip:2044@10.26.153.74:24334;transport=tcp>
Event: line-seize
User-Agent: PolycomSoundPointIP-SPIP_550-UA/4.0.4.2906
Accept-Language: en
Call-Info: <sip:10.66.30.20>;appearance-index=1
Content-Length: 0

------------------------------------------------------------------------
recv 408 bytes from tcp/[10.26.153.74]:24334 at 13:48:47.336088:
------------------------------------------------------------------------
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TCP 10.66.30.20:5065;branch=z9hG4bKjp5BSv4Sty39H
From: <sip:2044@10.66.30.20:5065>;tag=YIyjbbFm5Lol
To: "polycom 550" <sip:2044@10.66.30.20:5065>;tag=22064DE4-BCE24995
CSeq: 50006353 NOTIFY
Call-ID: d6f865f8-943b8209-fbabcd2@10.26.153.74
Event: line-seize
User-Agent: PolycomSoundPointIP-SPIP_550-UA/4.0.4.2906
Accept-Language: en
Content-Length: 0

------------------------------------------------------------------------
recv 664 bytes from tcp/[10.26.153.74]:45349 at 13:48:47.400123:
------------------------------------------------------------------------
SUBSCRIBE sip:2044@10.66.30.20:5065;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.26.153.74:24334;branch=z9hG4bK8d34b6939C4DDD8C
From: "polycom 550" <sip:2044@10.66.30.20:5065>;tag=22064DE4-BCE24995
To: <sip:2044@10.66.30.20:5065>;tag=YIyjbbFm5Lol
CSeq: 2 SUBSCRIBE
Call-ID: d6f865f8-943b8209-fbabcd2@10.26.153.74
Contact: <sip:2044@10.26.153.74:24334;transport=tcp>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
Event: line-seize
Call-Info: <sip:10.66.30.20>;appearance-index=1
User-Agent: PolycomSoundPointIP-SPIP_550-UA/4.0.4.2906
Accept-Language: en
Max-Forwards: 70
Expires: 0
Content-Length: 0

------------------------------------------------------------------------
send 762 bytes to tcp/[10.26.153.74]:45349 at 13:48:47.427039:
------------------------------------------------------------------------
SIP/2.0 202 Accepted
Via: SIP/2.0/TCP 10.26.153.74:24334;branch=z9hG4bK8d34b6939C4DDD8C;rport=45349
From: "polycom 550" <sip:2044@10.66.30.20:5065>;tag=22064DE4-BCE24995
To: <sip:2044@10.66.30.20:5065>;tag=YIyjbbFm5Lol
Call-ID: d6f865f8-943b8209-fbabcd2@10.26.153.74
CSeq: 2 SUBSCRIBE
Contact: <sip:2044@10.66.30.20:5065;transport=tcp>
Expires: 0
User-Agent: Freeswitch
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Subscription-State: terminated;reason=noresource
Content-Length: 0

------------------------------------------------------------------------
send 803 bytes to tcp/[10.26.153.74]:24334 at 13:48:47.427186:
------------------------------------------------------------------------
NOTIFY sip:2044@10.26.153.74:24334;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.66.30.20:5065;branch=z9hG4bKptaF0877e2vmg
Max-Forwards: 70
From: <sip:2044@10.66.30.20:5065>;tag=YIyjbbFm5Lol
To: "polycom 550" <sip:2044@10.66.30.20:5065>;tag=22064DE4-BCE24995
Call-ID: d6f865f8-943b8209-fbabcd2@10.26.153.74
CSeq: 70213599 NOTIFY
Contact: <sip:2044@10.66.30.20:5065;transport=tcp>
Expires: 0
User-Agent: Freeswitch
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Subscription-State: terminated;reason=noresource
Content-Length: 0

------------------------------------------------------------------------
recv 381 bytes from tcp/[10.26.153.74]:24334 at 13:48:47.546036:
------------------------------------------------------------------------
SIP/2.0 482 Loop Detected
Via: SIP/2.0/TCP 10.66.30.20:5065;branch=z9hG4bKptaF0877e2vmg
From: <sip:2044@10.66.30.20:5065>;tag=YIyjbbFm5Lol
To: "polycom 550" <sip:2044@10.66.30.20:5065>;tag=22064DE4-BCE24995
CSeq: 70213599 NOTIFY
Call-ID: d6f865f8-943b8209-fbabcd2@10.26.153.74
User-Agent: PolycomSoundPointIP-SPIP_550-UA/4.0.4.2906
Accept-Language: en
Content-Length: 0

------------------------------------------------------------------------

 

If this is not the proper venue to ask this question or if anyone needs any more detail I can provide it.  It is very hard to replicate this scenario to get it to fail consistently.  

 

 

Thank you everyone in advance.

2 REPLIES 2
HP Recommended

Hello Ron Stephens,

welcome to the Polycom Community.

The FreeSwitch community would most likely be a better place to ask FreeSwitch related questions.

 

From a Polycom perspective both these phones are running an outdated Software.

 

The SPIP sould run UCS 4.0.7 (4.1.0 and 4.1.1 is for LYNC only) and the VVX can run 4.1.8, 5.1.3 or even 5.2.0

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
HP Recommended

This eventually worked itself out by itself.  No changes were nessarry, it just started to 'work'.  I would preusme it was because of how the cseq value was computed in the first place.  from my understanding it was based on linux epoch time

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.