The response should be sent to the address where the BYE was received. 
Are you sure that the BYE is not still going through the proxy?

Message: 1
Date: Tue, 17 Mar 2015 12:40:09 +0000 (UTC)
From: Daniel Gomez <goll...@gmail.com>
Subject: [Sipp-users] 200OK answer to BYE is sent to incorrect IP
    address
To: sipp-users@lists.sourceforge.net
Message-ID: <loom.20150317t125009-...@post.gmane.org>
Content-Type: text/plain; charset=us-ascii

Hi,

I am using two sipp, as UAC and UAS, to test a Proxy.
This proxy does not add itself to Record-Route, then all messages out of 
initial INVITE transaction should go directly from UAS to UAC and 
viceversa.
I have found a problem in 200 OK answer to BYE (line 9 of scenario). 
Sipp UAS sends it to Proxy, instead of UAC.

      UAC             Proxy             UAS
    1- | ---INVITE----> |                |
    2- |                | ---INVITE----> |
    3- |                | <-100 Trying-- |
    4- | <-100 Trying-- |                |
    5- |                | <---200 OK---- |
    6- | <---200 OK---- |                |
    7- | --------------ACK ------------> |
    8- | --------------BYE ------------> |
    9- |                | <---200 OK---- |

xml scenario in UAS related to 200 has the following lines:
    <send >
    <![CDATA[
    
    SIP/2.0 200 OK
    [last_Via:]
    [last_From:]
    [last_To:]
    [last_Call-ID:]
    [last_CSeq:]
    Contact: <sip:[local_ip]:[local_port];transport=[transport]>
    Content-Length: 0
    
    ]]>
    </send>

In fact, a snoop captures shows that Via header has the expected value 
obtained from received BYE....:
    -----------------------------------------------
    2015-03-17 11:32:43:879.398
    UDP message received [372] bytes :
    
    BYE sip:service@172.21.2.111:48575 SIP/2.0
    Via: SIP/2.0/UDP 172.21.2.59:48675;branch=z9hG4bK-18607-1-11
    From: "942888888"<sip:942888...@ims.xxxxxxxx.es>;tag=1
    To: <sip:942999...@ims.xxxxxxxx.es>;tag=1
    Call-ID: 1-18607@172.21.2.59
    CSeq: 2 BYE
    Max-Forwards: 69
    Contact: <sip:172.21.2.111:48575;transport=UDP>
    Content-Length: 0
    User-Agent: Sipura/SPA841-3.1.3(a)
    -----------------------------------------------
    2015-03-17 11:32:43:879.554
    UDP message sent (290 bytes):
    
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 172.21.2.59:48675;branch=z9hG4bK-18607-1-11
    From: "942888888"<sip:942888...@ims.xxxxxxxx.es>;tag=1
    To: <sip:942999...@ims.xxxxxxxx.es>;tag=1
    Call-ID: 1-18607@172.21.2.59
    CSeq: 2 BYE
    Contact: <sip:172.21.2.111:48575;transport=UDP>
    Content-Length: 0
    
I expected sipp would send 200 Ok to the Via header of BYE messages.

Should I change something in xml to deal with this scenario ?

Thanks in advance
Daniel Gomez





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

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/

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

_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users


End of Sipp-users Digest, Vol 104, Issue 11
*******************************************
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to