[asterisk-bugs] [JIRA] (ASTERISK-25071) RFC3581 compliance

[Oleg Rabinovich (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-25071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226181#comment-226181 ] 

Oleg Rabinovich commented on ASTERISK-25071:
--------------------------------------------

Scenario description: 
- Two SIP clients (100 and 101) registering on Asterisk box via SIP proxy (Kamailio)
- One SIP client trying to call another one and the call fails.

Expected behavior: Asterisk to use a proxy address to call routing
Actual behavior: log message "[May 11 05:45:47] DEBUG[28030] chan_sip.c: Store REGISTER's Contact header for call routing." and as a result Asterisk sending INVITE directly to SIP client

Note: when enabled "nat=force_rport" option in sip.conf, the call works as expected, however, I would expect ";rport" option in "via" field of REGISTER request to make that effect.

> RFC3581 compliance
> ------------------
>
>                 Key: ASTERISK-25071
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25071
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Registration
>    Affects Versions: 13.3.2
>         Environment: CentOS 6.5
>            Reporter: Oleg Rabinovich
>            Assignee: Oleg Rabinovich
>         Attachments: extensions.conf, messages, reg_n_call.pcap, RFC3581.patch, sip.conf
>
>
> I am connecting to Asterisk via Kamailio SIP proxy (version 4.2.3). The client, MicroSIP-3.6.3 is behind NAT. Kamailio SIP proxy adds ";rport" to via headers in order to receive the traffic back from the server, according to RFC 3581. However, I fail to dial that client, as Asterisk dials directly to the client (public address) instead of my Kamailio box. This issue is similar to ASTERISK-7276, however, it's different in the sense that SIP request (INVITE) that is not routed correctly is a separate request from the one (REGISTER) that includes ";rport".
> I am attaching a patch that fixes the issue in my environment. Please, review it and let me know if this is a correct direction or am I missing something.



--
This message was sent by Atlassian JIRA
(v6.2#6252)