[asterisk-bugs] [JIRA] (ASTERISK-27089) pjsip: Switching from directmedia to T.38 doesn't use correct contact addresses.

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-27089:
------------------------------------

    Status: Open  (was: Triage)

> pjsip: Switching from directmedia to T.38 doesn't use correct contact addresses.
> --------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27089
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27089
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Bridges/bridge_native_rtp, Channels/chan_pjsip
>    Affects Versions: 13.16.0
>            Reporter: Richard Mudgett
>         Attachments: directmedia_reinvite_t38_pjsip_full.txt, directmedia_reinvite_t38_sip_full.txt
>
>
> If direct media is established before a T.38 reinvite switch is requested, chan_pjsip does not use the correct contact address.  It continues to use the remote addresses even thought the UDPTL ports are local.
> Scenario:
> # A calls B
> # Asterisk reinvites A and B to send media directly between A and B
> # A or B initiates a reinvite to start T.38
> # The contact addresses used by Asterisk in the T.38 reinvites are still the direct media addresses of A and B instead of Asterisk's own address while the T.38 stream's ports are Asterisk's port for the UDPTL traffic.
> The attached testsuite test logs for chan_sip and chan_pjsip show that chan_sip uses the expected address while chan_pjsip uses the wrong addresses.
> The full logs are from the respective testsuite tests:
> tests/fax/sip/directmedia_reinvite_t38
> tests/fax/pjsip/directmedia_reinvite_t38



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