Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Sip-Servlets MSS-3.0.0.FINAL Roadmap-Fix

New issue 269 by [email protected]: createBranch for a new SIP Request
http://code.google.com/p/sipservlets/issues/detail?id=269

What steps will reproduce the problem?
1.High possibility of simultaneous SIP requests creating the same branch parameter as it uses system.nanotime()

What is the expected output? What do you see instead?
The branch parameter is expected to be UNIQUE for each request.

What version of the product are you using? On what operating system?
MSS 2.0.0.FINAL

Please provide any additional information below.
I am using JBOSS 7 with Mobicents 2.0.0 for the application we are running. We have some sort of a heart beat (pinger) mechanism to check on the health of ICSCF from our application. To be more clear, there are 2 ICSCFs Primary and Secondary and we keep sending OPTIONS every configured seconds (10). The OPTIONS pings are sent successively to both Primary and Secondary and based on the failure we consider one of them as down and make sure the call is sent through the working ICSCF. It looks like the OPTIONS request created for Primary and Secondary has the same branch parameter since "System.nanoTime()" is what is being used while creating Branch for new requests. On searching about this, I do see a fix made in the link "https://code.google.com/p/mobicents/issues/detail?id=2278"; using "ApplicationRoutingHeaderComposer.randomString()". I am assuming that is a correct fix but just not sure why it wasn't merged on future versions. Please comment and let me know if otherwise.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

--- You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to