[asterisk-bugs] [JIRA] (ASTERISK-27971) res_pjsip: Implement additional SIP RFCs for Google Voice trunk compatability

[Dmitriy Serov (JIRA)]

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

Dmitriy Serov edited comment on ASTERISK-27971 at 10/10/18 5:25 AM:
--------------------------------------------------------------------

attachments gvoice.txt

Strange sequence REGISTER packets.
1. 423 Interval Too Brief
func handle_registration_response (res/res_pjsip_outbound_registration.c) does not have a handler of code 423.
I think there needs to be processing this code and call schedule_retry

2. Second REGISTER packet does not have "Supported: path"



was (Author: demon):
Strange sequence REGISTER packets.
1. 423 Interval Too Brief
func handle_registration_response (res/res_pjsip_outbound_registration.c) does not have a handler of code 423.
I think there needs to be processing this code and call schedule_retry

2. Second REGISTER packet does not have "Supported: path"


> 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
>         Attachments: gvoice.txt
>
>
> 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)
> - Outbound supported header (RFC 5626)
> - 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)