Bugs item #2284108, was opened at 2008-11-14 14:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2284108&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: trunk
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Norm Brandinger (norm_brandinger)
Assigned to: Nobody/Anonymous (nobody)
Summary: PRACK(100rel) problem with parallel forks

Initial Comment:
Testing two phones both (Aastra's and Polycom's with PRACK support that cannot 
be disabled) behind a NAT registering to OpenSIPS with the same name.  These 
tests were in support of PUA_BLA.

When an incoming call is made by an endpoint that also supports PRACK, (while 
both phones ring) only one of the two phones can be answered.

When an incoming call is made by an endpoint that does not support PRACK, both 
phones can be answered.

Tested using a SPA942 as the phone calling in (which allows PRACK(100rel) to be 
turned off) resolved the problem.

Tested with FreeSWITCH and it initially failed because (100rel was enabled by 
default).  When I turned off 100rel the problem went away.

I believe the problem is caused when the PRACK is being sent to endpoints that 
have been parallel forked by OpenSIPS.

Also, if I only use one Aastra/Polycom (powering the other one down), the 
single phone is able to be answered all the time.

The following thread first caused me to look into OpenSIPS and PRACK a little 
closer:

http://lists.opensips.org/pipermail/users/2008-August/000286.html

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2284108&group_id=232389

_______________________________________________
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

Reply via email to