Jump to content

Getting a ton of SIP SUBSCRIBE's from Polycom Phones


MarkW S7
 Share

Recommended Posts

We are seeing a ton of SUBSCRIBE's from only our Polycom customers and it's consuming a TON of CPU resources. Is anyone aware of a bug? We run pbx version 3.3 and the latest Polycom firmware. Any thoughts on how to reduce this?

 

I guess we are talking about a message like this:

 

[7] 20091216115340: SIP Rx tcp:192.168.4.104:63483:
SUBSCRIBE sip:48@pbx.company.com:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.168.4.104;branch=z9hG4bK4f6fee11C361DAE6
From: "Fourty Eight" <sip:48@pbx.company.com>;tag=7712E03B-A6163748
To: <sip:48@pbx.company.com>
CSeq: 2 SUBSCRIBE
Call-ID: 988c379c-477f92d5-f3ce2f5a@192.168.4.104
Contact: <sip:48@192.168.4.104;transport=tcp>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
Event: dialog
User-Agent: PolycomSoundPointIP-SPIP_550-UA/3.1.3.0439
Accept-Language: en
Accept: application/dialog-info+xml,application/rlmi+xml,multipart/related
Supported: eventlist
Authorization: Digest username="48", realm="pbx.company.com", nonce="1c874d174e18bb301d88f28b73213a33", uri="sip:48@pbx.company.com:5060;transport=tcp", response="a2d1469c8fdfb96d958eed462613d910", algorithm=MD5
Max-Forwards: 70
Expires: 120
Content-Length: 0

 

The PBX answers with:

 

[7] 20091216115341: SIP Tx tcp:192.168.4.104:63483:
SIP/2.0 404 Not Available
Via: SIP/2.0/TCP 192.168.4.104;branch=z9hG4bK4f6fee11C361DAE6
From: "Fourty Eight" <sip:48@pbx.company.com>;tag=7712E03B-A6163748
To: <sip:48@pbx.company.com>;tag=1f8da3cef2
Call-ID: 988c379c-477f92d5-f3ce2f5a@192.168.4.104
CSeq: 2 SUBSCRIBE
Retry-After: 3600
Content-Length: 0

 

The problem is that the phone retries after a few seconds, not one hour (see http://www.ietf.org/rfc/rfc3265.txt). That's okay for small installations; however for large deployments a pain in the neck.

 

What you can do is setting the "Watch the calls of the following extensions " for the extension to one extension (better don't use star because in large deployments, this will create an even bigger mess), then the phone respects the duration and will happily show the status on that extension.

 

Not sure if a firmware update solves that problem or there is a setting available that slows down the retry (there are a lot of parameters in the xml configuration files). We will investigate if there are more feasable workarounds for this problem.

Link to comment
Share on other sites

  • 1 month later...
We are seeing a ton of SUBSCRIBE's from only our Polycom customers and it's consuming a TON of CPU resources. Is anyone aware of a bug? We run pbx version 3.3 and the latest Polycom firmware. Any thoughts on how to reduce this?

 

This was addressed in a fix to the PBX and is no longer an issue. I just was clarifying that this is complete.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...