[asterisk-bugs] [JIRA] (ASTERISK-27971) res_pjsip: Implement additional SIP RFCs for Google Voice trunk compatability
Joshua Colp (JIRA)
noreply at issues.asterisk.org
Wed Jul 18 07:35:54 CDT 2018
[ https://issues.asterisk.org/jira/browse/ASTERISK-27971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Colp updated ASTERISK-27971:
-----------------------------------
Assignee: Nick French
> res_pjsip: Implement additional SIP RFCs for Google Voice trunk compatability
> -----------------------------------------------------------------------------
>
> Key: ASTERISK-27971
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-27971
> Project: Asterisk
> Issue Type: New Feature
> Security Level: None
> Components: pjproject/pjsip, Resources/res_pjsip_outbound_registration
> Affects Versions: GIT
> Reporter: Nick French
> Assignee: Nick French
> Labels: pjsip
>
> Background: Google Voice trunks are currently supported in Asterisk via chan_motif. Google has announced they plan to migrate away from the XMPP protocol used by chan_motif to a new SIP-based protocol. However, their new SIP servers use additional standards extending what is commonly implemented in a SIP UAC.
> The following additional features required by the new Google Voice SIP registrar are not currently implemented in Asterisk:
> - Service-Routes (RFC 3608)
> - P-Preferred-Identity (RFC 3325)
> - OAuth / Bearer token authentication (draft-ietf-sipcore-sip-authn-02)
> - Mechanisms to use separate TLS transports for separate registrations and their associated message dialog
> - (optional) User-configurable additions to SIP Contact header
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list