Changes between Version 1 and Version 2 of Ticket #352


Ignore:
Timestamp:
Jul 10, 2007 1:51:32 AM (17 years ago)
Author:
bennylp
Comment:

Additional note: SER/iptel.org is also known to produce wrong Via sent-by, so in this case the UA will need to disable Via sent-by checking too.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #352 – Description

    v1 v2  
    77 
    88 
    9 This check is done in sip_endpoint.c::endpt_on_rx_msg(). When PJSIP drops the request with wrong sent-by, a message like this will be printed to the log: ''Dropping response Response msg 200/INVITE/cseq=608594373 (rdata00A99EF4) from 213.192.59.75:5060 because sent-by is mismatch"'' 
     9This check is done in sip_endpoint.c::endpt_on_rx_msg(). When PJSIP drops the request with wrong sent-by, a message like this will be printed to the log:  
     10 
     11''Dropping response Response msg 200/INVITE/cseq=608594373 (rdata00A99EF4) from 1.2.3.4:5060 because sent-by is mismatch"'' 
    1012 
    1113With the UA supporting IP address change, it is possible that the Via sent-by in the response is no longer recognized as the UAC's transport address, even when the UAS doesn't modify this Via sent-by values. This happens when the UAC has changed its transport IP address after it sent the request, but before response is received. In this case, the response will be dropped.