| Summary: | ASTERISK-27089: pjsip: Switching from directmedia to T.38 doesn't use correct contact addresses. | ||
| Reporter: | Richard Mudgett (rmudgett) | Labels: | |
| Date Opened: | 2017-06-28 12:19:34 | Date Closed: | |
| Priority: | Major | Regression? | |
| Status: | Open/New | Components: | Bridges/bridge_native_rtp Channels/chan_pjsip |
| Versions: | 13.16.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) directmedia_reinvite_t38_pjsip_full.txt ( 1) directmedia_reinvite_t38_sip_full.txt | |
| Description: | 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 | ||
| Comments: | |||