[asterisk-users] [asterisk13] Multiple transport objects of same protocol in pjsip.conf
Antony.Stone at asterisk.open.source.it
Sat Jul 29 13:17:07 CDT 2017
On Saturday 29 July 2017 at 19:03:55, Joshua Colp wrote:
> On Sat, Jul 29, 2017, at 02:55 PM, O. Hartmann wrote:
> > Scenario:
> > Our Asterisk 13 PBX (on network 192.168.254.0/24, bound to
> > 192.168.254.1:5060) is behind
> > a NAT, acting as a client to our ITSPs SIP server. But also, this
> > Asterisk is server for
> > various VoIP telephones.
> > Acoording to Asterisk's wiki, the transport section of pjsip.conf is
> > configured as
> > follows:
> > ; Transport via UDP
> > [transport-nat-udp]
> > type= transport
> > protocol= udp
> > local_net= 192.168.254.0/24
> > local_net= 127.0.0.1/32
> > bind= 192.168.254.1:5060
> > external_media_address= ddns.gdr
> > external_signaling_address= ddns.gdr
> You should only need this single transport as it will get used by
> everything. Only when contacting external things will the external
> values be used instead. This is determined based on the "local_net"
> values you've provided.
Also, setting a transport to expect NAT, when in fact there isn't any, won't
Telling Asterisk to expect NAT simply means that it pays attention to where
the packets come from, not what addresses they contain inside them.
If you have no NAT, these two addresses are the same, so no harm done.
Bill Gates has personally assured the Spanish Academy that he will never allow
the upside-down question mark to disappear from Microsoft word-processing
programs, which must be reassuring for millions of Spanish-speaking people,
though just a piddling afterthought as far as he's concerned.
- Lynne Truss, "Eats, Shoots and Leaves"
Please reply to the list;
please *don't* CC me.
More information about the asterisk-users