[asterisk-bugs] [JIRA] (ASTERISK-26988) res_pjsip_session: user_eq_phone adds double user=phone parameters to URIs on re-Invite

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-26988:
-----------------------------------

    Assignee: dtryba  (was: Unassigned)
      Status: Waiting for Feedback  (was: Open)

If you try the change at https://gerrit.asterisk.org/#/c/5535/ does this resolve the problem?

> res_pjsip_session: user_eq_phone adds double user=phone parameters to URIs on re-Invite
> ---------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26988
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26988
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_session
>    Affects Versions: 13.14.1
>         Environment: Debian/stretch with repository supplied Asterisk 13.14.1~dfsg-1
> There are no updates/patches for user_eq_phone either Debian specific or from 13.41.1 to 13.15 as far as I can see.
>            Reporter: dtryba
>            Assignee: dtryba
>            Severity: Minor
>         Attachments: dialplan.txt, full.txt, invites.txt, pjsip.conf.txt
>
>
> Asterisk in a setup as proxy/sbc between customer and upstream provider, where upstream demands the use of user=phone for URIs containing phonenumbers. Only the endpoint definitions for upstream contain the "user_eq_phone = yes" option.
> INVITE from upstream to Asterisk. R-URI/To/From/PAI containt the user=phone params. INVITE from Asterisk to customer, the user=phone gets stripped from all URIs. The 1xx/200OK from customer lack user=phone, but gets added by Asterisk to upstream. So far so good.
> The customer endpoint is a fax, that re-INVITEs for t38. The re-INVITE lack user=phone. Asterisk adds "user=phone;user=phone" to relevant URIs
> Upstream provider answers with a "400 Bad Request" and the connection is terminated (by both upstream as Asterisk). 



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