• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
[FAQ] How can I set up a conference or how many participants can be in the conference?, Click here to find out!
Locked

‎04-23-2013 12:29 PM

HP Recommended

Hello community,

 

I'm trying to find out if there's a configuration option within 3.2.X or 4.0.X to force regeneration of call-id upon REGISTER. I have combed through the admin guides and Polycom site for information but I have not been able to find anything on the topic so far. RFC 3261 states this is possible :

 

( http://tools.ietf.org/html/rfc3261#section-8.1.1.4 )
8.1.1.4 Call-ID

   The Call-ID header field acts as a unique identifier to group
   together a series of messages.  It MUST be the same for all requests
   and responses sent by either UA in a dialog.  It SHOULD be the same
   in each registration from a UA.

 

SHOULD != MUST but I'm thinking it may not be supported by Polycom. I did find an explination of why it "SHOULD" be the same here :

 

( https://lists.cs.columbia.edu/pipermail/sip-implementors/2002-October/003963.html )
The requirement that an UA SHOULD use the same call-id for all registration during a single boot cycle is to ensure sequencing of the Register requests. It ensures that an out-of-order REGISTER request doesnot do any harm. (change or remove a binding registered by a REGISTER request sent after it). Section 10.3, step 8 explains the processing of the Registrar w.r.t to callids.

 

Regards,

Matt

 

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.
Didn't find what you were looking for? Ask the community
† 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>.