asterisk users - Jan 2020 - Solved: Re: Asterisk 13.18.3 PJSIP. Wrong Port in Contact Header in Reply to REGISTER?

Hi Joshua

Thank you for your reply.

Indeed, Ubuntu only ships with this old version. Upgraded to 16.2. via
PPA. Problem persisted.

Well, I already mentioned that this is a machine with two physical
interfaces with different routes which on the 'external' side handles
SIP customer registrations and has an 'internal' IC Trunk to a
commercial Voice Switch via private IP Range.

I had the problem, that some of the packets sent out on the 'external'
side contained 'private' IP addresses in either signaling or SDP.

So I threw all options I could find into the config to bind
transports, endpoints, media and so on to the corresponding interface ip
address. First this looked good. I had the correct IP in every header
and SDP I expected.

well setting under transport:

external_signaling_address=[local IP]

Assuming this is the own interface IP that would be told to external
endpoints was obviously wrong.

In the end this caused the Proxy-SBC to believe it was not getting an
OK to it's forwarded registration and discard this session.

Mit freundlichen Grüssen

-Benoît Panizzon-
-- 
I m p r o W a r e   A G    -    Leiter Commerce Kunden
______________________________________________________

Zurlindenstrasse 29             Tel  +41 61 826 93 00
CH-4133 Pratteln                Fax  +41 61 826 93 01
Schweiz                         Web  http://www.imp.ch
______________________________________________________

Well, not so solved unfortunately...

Now I am back to where I have the situation the Asterisk sends out 183
Media Progress from one interface, containing a Contact Header with the
local IP of the other interface breaking audio.

Is there any way to completely bind all IP Addresses within headers
sent out one interface to the IP of that interface?

Mit freundlichen Grüssen

-Benoît Panizzon-
-- 
I m p r o W a r e   A G    -    Leiter Commerce Kunden
______________________________________________________

Zurlindenstrasse 29             Tel  +41 61 826 93 00
CH-4133 Pratteln                Fax  +41 61 826 93 01
Schweiz                         Web  http://www.imp.ch
______________________________________________________

On Mon, Jan 13, 2020 at 11:10 AM Benoit Panizzon <benoit.panizzon at
imp.ch>
wrote:
> Well, not so solved unfortunately...
>
> Now I am back to where I have the situation the Asterisk sends out 183
> Media Progress from one interface, containing a Contact Header with the
> local IP of the other interface breaking audio.
>
> Is there any way to completely bind all IP Addresses within headers
> sent out one interface to the IP of that interface?
>
Configuring individual PJSIP transports bound to the specific IP addresses
and then configuring the transport explicitly on things may do such a
thing.

-- 
Joshua C. Colp
Asterisk Technical Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20200113/be2b8e2a/attachment.html>

Hello,

Days ago, I banged on a similar issue with Debian Buster's asterisk (16.2):
my box had two interfaces (one North and one South) both with private
addresses
when relaying calls from South to North, my box used South Address for
media handling.

Upgrading to 16.7.0 without changing configuration, immediately solved the
issue.

I didn't have time to dig into this (ie reading Changelogs or debugging
step by step).
I don't think my config was perfect either but if I had to implement
anything on Debian Buster again, I'll prepare myself to spend some times on
this.

My 0.01 cent

Le lun. 13 janv. 2020 à 15:51, Benoit Panizzon <benoit.panizzon at imp.ch>
a
écrit :
> Hi Joshua
>
> Thank you for your reply.
>
> Indeed, Ubuntu only ships with this old version. Upgraded to 16.2. via
> PPA. Problem persisted.
>
> Well, I already mentioned that this is a machine with two physical
> interfaces with different routes which on the 'external' side
handles
> SIP customer registrations and has an 'internal' IC Trunk to a
> commercial Voice Switch via private IP Range.
>
> I had the problem, that some of the packets sent out on the
'external'
> side contained 'private' IP addresses in either signaling or SDP.
>
> So I threw all options I could find into the config to bind
> transports, endpoints, media and so on to the corresponding interface ip
> address. First this looked good. I had the correct IP in every header
> and SDP I expected.
>
> well setting under transport:
>
> external_signaling_address=[local IP]
>
> Assuming this is the own interface IP that would be told to external
> endpoints was obviously wrong.
>
> In the end this caused the Proxy-SBC to believe it was not getting an
> OK to it's forwarded registration and discard this session.
>
> Mit freundlichen Grüssen
>
> -Benoît Panizzon-
> --
> I m p r o W a r e   A G    -    Leiter Commerce Kunden
> ______________________________________________________
>
> Zurlindenstrasse 29             Tel  +41 61 826 93 00
> CH-4133 Pratteln                Fax  +41 61 826 93 01
> Schweiz                         Web  http://www.imp.ch
> ______________________________________________________
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> Check out the new Asterisk community forum at:
> https://community.asterisk.org/
>
> New to Asterisk? Start here:
>       https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20200117/fc9f8e52/attachment.html>