[asterisk-bugs] [JIRA] (ASTERISK-28551) IPv4 address in SDP o= is (null) when configured for NAT using pjsip
George Joseph (JIRA)
noreply at issues.asterisk.org
Tue Sep 24 11:18:47 CDT 2019
[ https://issues.asterisk.org/jira/browse/ASTERISK-28551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=248124#comment-248124 ]
George Joseph commented on ASTERISK-28551:
------------------------------------------
The hostnames are resolved when the transport loads then at the interval specified in the dnsmgr.conf file.
Good point about the warning/error. I'll create an internal issue for that.
> 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)
More information about the asterisk-bugs
mailing list