Hi Alekzander,

I must say that I'm quite puzzled, as your use case works like a charm at my place (just tested it, using exactly your via header example)... The comments in the source code you refered to are not 100% accurate anymore. Reading a bit further, it is quite clear that SEMS does, in fact, respect the topmost via port if the ";rport" attribute is not present. The only thing that SEMS does not respect is the hostname, which is always taken from the request's IP header.

Would you have a PCAP trace file of the issue?

-Raphael.

On 04.04.11 07:46, Alekzander Spiridonov wrote:
It looks like:

Via: SIP/2.0/UDP 94.25.111.28:5060;wlsscid=-40d94a935cd12af0;maddr=94.25.111.28;branch=z9hG4bK83c94213c8c76642c50fb7aeb4f89d35

And comes from:
94.25.111.28:54041 <http://94.25.111.28:54041>


2011/4/1 Vladimir Broz <[email protected] <mailto:[email protected]>>

    Please, how does the incoming Via header look like exactly?

    Thanks,
    -Vlada B.



    On 04/01/2011 03:57 PM, Alekzander Spiridonov wrote:

        - 18.2.2 Sending Responses

        We have a UAC that sends INVITE from a random port but sets
        the Via
        header to host:5060 and expects to receive response from UAS
        (SEMS) on
        port 5060. But SEMS still sends response to that random port.

        Is it related to ./sems-1.4.0/core/sip/trans_layer.cpp:
        "
            // TODO: Inspect topmost 'Via' and select proper addr
        (+resolve DNS
        names)
            // refs: RFC3261 18.2.2; RFC3581
        "

        2011/4/1 Vladimir Broz <[email protected]
        <mailto:[email protected]> <mailto:[email protected]
        <mailto:[email protected]>>>


           Hi,


           On 04/01/2011 03:12 PM, Alekzander Spiridonov wrote:

               Hi,

               SEMS sends SIP-reply not to the host:port from the Via
        field,
               but to the
               host and port it received request from. Is there any
        way to fix it?

           could you be more specific? What exactly SEMS does not
        comply to?
           Please, check the sections:
           - 18.2.1 Receiving Requests
           - 18.2.2 Sending Responses

           BR,
           -Vlada B.


               --
               Best regards,
               Alekzander Spiridonov




               _______________________________________________
               Sems mailing list
        [email protected] <mailto:[email protected]>
        <mailto:[email protected] <mailto:[email protected]>>

        http://lists.iptel.org/mailman/listinfo/sems




        --
        С уважением,
        Александр Спиридонов




        _______________________________________________
        Sems mailing list
        [email protected] <mailto:[email protected]>
        http://lists.iptel.org/mailman/listinfo/sems




--
Best regards,
Alekzander Spiridonov



_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to