Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 2278 by [email protected]: the "branch" parameter in Via header duplicated in different SIP transaction
http://code.google.com/p/mobicents/issues/detail?id=2278

What steps will reproduce the problem?
1.When receiving a http request, run a B2BUA between user A and user B, send a SIP Invite from the http servlet to user A (without sdp part) 2.When receiving the 200ok from user A, send a new Invite to user B with the sdp of user A. 3.When receiving the 200ok from user B, send back a Ack to user B and send back a Ack with the sdp of user B to user A. 4.sometimes, when the sip server try to send the Invite packet to user B, the "javax.sip.TransactionUnavailableException: Transaction already exists!" error occurs.



What is the expected output? What do you see instead?

The branch parameter should be unique in each transactions.

What version of the product are you using? On what operating system?
OS-System: Linux 2.6.32-gentoo-r7,i386
Java version: 1.6.0_22,Sun Microsystems Inc.
VM arguments: -Dprogram.name=run.sh -Xms1700m -Xmx1700m -XX:MaxPermSize=256m -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:NewRatio=3 -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/opt/mss-1.6.0-SNAPSHOT-jboss-jdk6-5.1.0.GA/lib/endorsed

mss-1.6.0-SNAPSHOT-jboss-jdk6-5.1.0.GA-1101150413-LGPL.zip
Release ID: (Mobicents) Sip Servlets 1.6.0-SNAPSHOT (build: SVNTag=r16564 date=${maven.build.timestamp})


Please provide any additional information below.

This problem seems not to happen in MSS-1.4.0 final, but it happens in MSS-1.5.0 and MSS-1.6.0-SNAPSHOT.

maybe two Invite is created in the same time, the branch id would be the same?


The attachment files contains tcpdump files and log files.
the tcpdump files can be view via wireshark, and set the filter expression to "sip contains [branch_id]", e.g. "sip contains z9hG4bKc023710c-6400-4188-bd7a-b07dbb7d109f_d1bcdd12_6466491921738014".


Attachments:
        transaction_exist_03.txt  59.6 KB
        transaction_exist_03.pcap  191 KB
        transaction_exist_02.pcap  142 KB
        transaction_exist_02.txt  43.7 KB

Reply via email to