# Some transport settings ignored when transport is not explicitely set **URL:** \ **Category:** Asterisk SIP\ **Created:** [June 2, 2026, 10:43am UTC](https://community.asterisk.org/t/some-transport-settings-ignored-when-transport-is-not-explicitely-set/113096 "2026-06-02T10:43:29Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![oza4h07](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/oza4h07/32/8735_2.png) [@oza4h07](https://community.asterisk.org/u/oza4h07)\ **Post date:** [June 2, 2026, 10:43am UTC](https://community.asterisk.org/t/some-transport-settings-ignored-when-transport-is-not-explicitely-set/113096/1 "2026-06-02T10:43:29Z")
Hello, On an Asterisk 22.0.0 instance, I’ve observed the following behaviour. This instance is running a cloud host with two public IPv4 IPs. One of these IP is a floating one (ie it can be easily moved from one host to another one) while the other one cannot be reused on another host. The default IP is the fixed one. So, to be able to move one day Asterisk t host to a different, I’m configuring a “simpletrans” PJSIP transport with the following [redacted] content (1.2.3.4 being the floating IP): ```auto [simpletrans] type=transport protocol=udp bind=1.2.3.4:5060 external_media_address=1.2.3.4 external_signaling_address=1.2.3.4 ``` This transport is the only one defined in my config. On the other hand, I’ve got an endpoint for which “transport=simpletrans” is ABSENT from pjsip.conf. For this endpoint, I’ve got no audio with the following details: - SDP mentions the floating IP - Signalling uses floating IP - RTP stream is sent from fixed IP (not the floating one). When for the same “transport=simpletrans” is PRESENT, all the above applies except that this time RTP stream is sent from the floating one and I can hear audio. Can you reproduce this (on a later Asterisk LTS 22 version if more practical) ? How would you qualify this ? Best regards ---
**Author:** ![jcolp](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/jcolp/32/8848_2.png) [@jcolp](https://community.asterisk.org/u/jcolp)\ **Post date:** [June 2, 2026, 10:49am UTC](https://community.asterisk.org/t/some-transport-settings-ignored-when-transport-is-not-explicitely-set/113096/2 "2026-06-02T10:49:18Z")
I don’t know why specifying a transport would do that, it should all be the same, but a transport controls what is bound for the SIP signaling and what goes in the SDP. It doesn’t control what is bound for RTP, and by default it will do wildcard so it is then up to the routing table to determine what interface and source IP address is used. If you want to be explicit then an option would be to set “media\_address”[1] and “bind\_rtp\_to\_media\_address”[2] on the endpoint. [1] [res\_pjsip - Asterisk Documentation](https://docs.asterisk.org/Latest_API/API_Documentation/Module_Configuration/res_pjsip/#media_address) [2] [res\_pjsip - Asterisk Documentation](https://docs.asterisk.org/Latest_API/API_Documentation/Module_Configuration/res_pjsip/#bind_rtp_to_media_address) ---
**Author:** ![oza4h07](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/oza4h07/32/8735_2.png) [@oza4h07](https://community.asterisk.org/u/oza4h07)\ **Post date:** [June 3, 2026, 7:52am UTC](https://community.asterisk.org/t/some-transport-settings-ignored-when-transport-is-not-explicitely-set/113096/3 "2026-06-03T07:52:26Z")
OK. Thanks for replying Le mar. 2 juin 2026 à 13:01, jcolp \<[notifications@asterisk.discoursemail.com](mailto:notifications@asterisk.discoursemail.com)\> a écrit : > Someone replied to a topic you are Watching. > > | ![](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/jcolp/45/8848_2.png "jcolp") | [jcolp](https://community.asterisk.org/u/jcolp) Asterisk Project Lead > June 2 | > | --- | --- | > > I don’t know why specifying a transport would do that, it should all be the same, but a transport controls what is bound for the SIP signaling and what goes in the SDP. It doesn’t control what is bound for RTP, and by default it will do wildcard so it is then up to the routing table to determine what interface and source IP address is used. If you want to be explicit then an option would be to set “media\_address”[1] and “bind\_rtp\_to\_media\_address”[2] on the endpoint. > > [1] [res\_pjsip - Asterisk Documentation](https://docs.asterisk.org/Latest_API/API_Documentation/Module_Configuration/res_pjsip/#media_address) > > [2] [res\_pjsip - Asterisk Documentation](https://docs.asterisk.org/Latest_API/API_Documentation/Module_Configuration/res_pjsip/#bind_rtp_to_media_address) > > * * * > > [Visit Topic](https://community.asterisk.org/t/some-transport-settings-ignored-when-transport-is-not-explicitely-set/113096/2) or reply to this email to respond. > > You are receiving this because you enabled mailing list mode. > > To unsubscribe from these emails, click here. ---
**Author:** ![system](https://global.discourse-cdn.com/asterisk/original/2X/4/475d0c889911cfb84ac4881ad6df8b523e3f9105.png) [@system](https://community.asterisk.org/u/system)\ **Post date:** [July 3, 2026, 7:52am UTC](https://community.asterisk.org/t/some-transport-settings-ignored-when-transport-is-not-explicitely-set/113096/4 "2026-07-03T07:52:57Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.