[asterisk-bugs] [JIRA] (ASTERISK-28551) IPv4 address in SDP o= is (null) when configured for NAT using pjsip

[Brian J. Murrell (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=248114#comment-248114 ] 

Brian J. Murrell commented on ASTERISK-28551:
---------------------------------------------

OK.  Figured out the issue:

{noformat}
; You can have more than one of any type of transport, as long as it doesn't
; use the same resources (bind address, port, etc) as the others.
{noformat}

In all of the messing around to get it figure out, I had both a {{transport-tcp-ipv4-nat}} and {{transport-tcp}} defined with the same bind addresses.

Additionally, it seems changing transports, particularly things to do with {{local_net}} requires an Asterisk restart, not just a {{pjsip reload}}.

Of course, having both {{transport-tcp-ipv4-nat}} and {{transport-tcp}} defined is not really necessary as as Asterisk will determine if the client is across the NAT from it and therefore needs to employ }{{external_media_address}} and/or {{external_signaling_address}}.

As an aside, if either of the {{external_*_address}} values is a hostname, when is that name resolved to an IP address?

Perhaps some other result than invalid SDP would be better in this type of case.  I would think that if that value ends up being {{(null)}} some kind of error or warning on the console would be useful.  It took quite some digging to even figure out that was the symptom.


> IPv4 address in SDP o= is (null) when configured for NAT using pjsip
> --------------------------------------------------------------------
>
>                 Key: ASTERISK-28551
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28551
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.28.1
>            Reporter: Brian J. Murrell
>            Assignee: Unassigned
>              Labels: fax, pjsip
>
> If I configure my pjsip transport to handle NAT from the Internet:
> {noformat}
> [transport-tcp]
> type=transport
> protocol=tcp
> bind=10.75.22.8:5060
> local_net=10.75.22.0/24
> external_media_address=[external address redacted]
> external_signaling_address=[external address redacted]
> {noformat}
> When a call comes from a TCP registered SIP client on the Internet,
> Asterisk is setting the IPv4 address in the {{o=}} and {{c=}} lines of the
> SDP ICE payload to {{(null)}}:
> {noformat}
> v=0
> o=- 3654 548 IN IP4 (null)
> s=Asterisk
> c=IN IP4 (null)
> {noformat}
> IPv4 addresses in all of the {{a=}} lines are still correct.
> This {{(null)}} of course causes the caller to fail to complete the call.



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