[asterisk-bugs] [JIRA] (ASTERISK-16884) [patch] add Path header support to chan_sip

[Olle Johansson (JIRA)]

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

Olle Johansson commented on ASTERISK-16884:
-------------------------------------------

Discovered a bug in the 1.8 patch that works in the 1.4 version. Will need to check why OPTIONS messages are not routed according to the route header. The Route: header is added (based on Path in the REGISTER) but we still transmit to the Contact. 

The wonders of the TCP/TLS patch messing with routing I guess.
                
> [patch] add Path header support to chan_sip
> -------------------------------------------
>
>                 Key: ASTERISK-16884
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-16884
>             Project: Asterisk
>          Issue Type: New Feature
>          Components: Channels/chan_sip/NewFeature
>            Reporter: klaus3000
>         Attachments: path-1.8.0-patch.txt
>
>
> This patch adds Path header support (RFC 3327) to Asterisk. You just have to activate "usepath=yes" in sip.conf for the peer.
> ****** ADDITIONAL INFORMATION ******
> currently the Path header is parsed (re-using the Record-Router parser) and stored in the peer structure. It is also stored/read to/form astDB. Realtime support is missing yet (any hints are appreciated).
> I did basic testing and it worked so far (it is almost impossible to understand to which destination the request will finally be sent (global OBP, peer OBP, nat=yes, ...). Some of these decisions are done in Asterisk during REGISTER handling, some are done during message sending. IMO it should be only done during message sending)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira