[asterisk-bugs] [JIRA] (ASTERISK-23994) res_pjsip_sdp_rtp: owner address in SDP may not be fully qualified domainname

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-23994:
----------------------------------------

{quote}
a) This is not how the old chan_sip works
{quote}

Using {{chan_sip}} as a reason to do something is not a valid argument. {{chan_sip}} does many things; some are wrong. In this case, the RFC is clearly fine with sending a fully qualified domain name; whether or not {{chan_sip}} does such a thing is immaterial to the issue.

{quote}
b) It will break interoperability with many SIP endpoints
{quote}

It breaks interoperability with a broken provider. That is all we can conclude at this point.

{quote}
c) This should be configurable by the user in pjsip.conf. In fact, this information should come only from the Transport which is associated with the outgoing endpoint.
{quote}

Asterisk is open source. If you'd like to add such an option, feel free to provide a patch to this issue that does that.

The bug here, however, is not the lack of an IPv4 or IPv6 address.

{quote}
d) Nobody has fully configured machine names that really map to an IP address. It just does not happens in the real world.
{quote}

I think a fair number of people use DNS.

{quote}
e) It is change so profound that is constitutes a bug.
{quote}

It is not a change in the PJSIP stack's implementation in Asterisk. It is different from {{chan_sip}}.

Again, luckily for you, Asterisk is open source. If you'd like it to provide an IPv4 or IPv6 address only, a patch that made that option would be just fine. It should not be the default behaviour, as the RFC is more than happy with a FQDN. In fact, given aspects of DNS fail over, a FQDN would be preferable in many circumstances.

If you can't provide such a patch, you can of course wait for someone to provide one for you. As far as I'm concerned, fixing the issue I've described here is more than enough to fix this bug.

I won't argue this point further.

> res_pjsip_sdp_rtp: owner address in SDP may not be fully qualified domainname
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-23994
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23994
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_sdp_rtp
>    Affects Versions: 12.3.2
>         Environment: Linux any version
>            Reporter: Private Name
>
> I already asked this question to the list and nobody answered, therefore it is a bug. The SDP-Owner section is wrong. This is what my client said:
> {quote}
> "That OK message from 1.1.1.1 can not be parsed by our switch due to
> address representation in their SDP:
> Owner/Creator, Session Id (o): Pitcom 2723451647 2723451649 IN IP4 Pitcomlxc
> Such address representation not supported, there should be IP address
> instead of domain name.
> Example:
> {noformat}
> Owner/Creator, Session Id (o): Pitcom 2723451647 2723451649 IN IP4 1.1.1.1
> {noformat}
> In fact, I traced it in the SDP packet, I see
> {noformat}
> o=Pitcom 3991413436 3 IN IP4 pitcomlxc
> {noformat}
> where pitcomlxc is the host name.
> {quote}
> How do I make PJSIP use an IP address there instead of the host name?
> My /etc/hosts.com has an entry for pitcomlxc, but it makes no difference.



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