[asterisk-bugs] [JIRA] (ASTERISK-26011) [patch]PJSIP: add "via_addr", "via_port", "call_id" to contacts

Matt Jordan (JIRA) noreply at issues.asterisk.org
Tue Jul 5 11:43:57 CDT 2016


     [ https://issues.asterisk.org/jira/browse/ASTERISK-26011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan closed ASTERISK-26011.
----------------------------------

    Resolution: Fixed

> [patch]PJSIP: add "via_addr", "via_port", "call_id" to contacts
> ---------------------------------------------------------------
>
>                 Key: ASTERISK-26011
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26011
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/res_pjsip, Resources/res_pjsip_registrar
>    Affects Versions: 13.9.0
>            Reporter: Alexei Gradinari
>            Severity: Minor
>
> As res_pjsip_nat rewrites contact's address, only the last Via header can contain the source address of registered endpoint.
> Also Call-Id header may contain the source address of registered endpoint.
> Added "via_addr", "via_port", "call_id" to contacts.
> Added new fields ViaAddress,CallID to AMI event ContactStatus.
> [edit by Rusty - adding Alexei's further explanation]
> To manually manage/provisioning remote (behind the NAT) SIP devices it's necessary to know internal ip-address.
> We could get internal ip-address using old-SIP AMI command 'SIPShowPeer'
> For example
> Reg-Contact : sip:user at 192.168.1.2:5060
> Using PJSIP we couldn't because res_pjsip_nat rewrites contact's address before
> AMI event is sent.
> To find out internal ip-address 2 SIP headers can help: Via and Call-Id.



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



More information about the asterisk-bugs mailing list