[asterisk-bugs] [JIRA] (ASTERISK-29961) RLS: domain part of 'uri' list attribute mismatch with SUBSCRIBE request

Asterisk Team (JIRA) noreply at issues.asterisk.org
Wed Mar 9 16:07:07 CST 2022


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

Asterisk Team commented on ASTERISK-29961:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> RLS: domain part of 'uri' list attribute mismatch with SUBSCRIBE request
> ------------------------------------------------------------------------
>
>                 Key: ASTERISK-29961
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29961
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_pubsub
>    Affects Versions: 16.24.1, 18.10.1, 19.2.1
>            Reporter: Alexei Gradinari
>
> When asterisk generates the RLMI part of NOTIFY request, the asterisk uses the local contact uri instead of the URI to which the SUBSCRIBE request is sent.
> Because of this mismatch some IP phones (for example Cisco 5XX) ignore this list.
> According
> https://datatracker.ietf.org/doc/html/rfc4662#section-5.2
>    The first mandatory <list> attribute is "uri", which contains the uri
>    that corresponds to the list.  Typically, this is the URI to which
>    the SUBSCRIBE request was sent.
> https://datatracker.ietf.org/doc/html/rfc4662#section-5.3
>    The "uri" attribute identifies the resource to which the <resource>
>    element corresponds.  Typically, this will be a SIP URI that, if
>    subscribed to, would return the state of the resource.
> For example if the SUBSCRIBE request is sent to
> sip:rls_1004 at asterisk.company.com
> the asterisk generates the next RLMI
> --dtqzb
> Content-ID: <lflen at 192.168.100.15>
> Content-Type: application/rlmi+xml
> Content-Length:   483
> <?xml version="1.0" encoding="UTF-8"?>
> <list xmlns="urn:ietf:params:xml:ns:rlmi" uri="sip:rls_1004 at 192.168.100.15:5060" version="1" fullState="false">
>  <name>rls_1004</name>
>  <resource uri="sip:1001 at 192.168.100.15:5060">
>   <name>Alice</name>
>   <instance id="smgzj" state="active" cid="bqgdu at 192.168.100.15" />
>  </resource>
> </list>
> --dtqzb
> Content-ID: <bqgdu at 192.168.100.15>
> Content-Type: application/dialog-info+xml
> Content-Length:   230
> <?xml version="1.0" encoding="UTF-8"?>
> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="39" state="full" entity="sip:1001 at 192.168.100.15:5060">
>  <dialog id="1001">
>   <state>confirmed</state>
>  </dialog>
> </dialog-info>
> Better if asterisk would generate RLMI
> --tswyz
> Content-ID: <uzogh at asterisk.company.com>
> Content-Type: application/rlmi+xml
> Content-Length:   518
> <?xml version="1.0" encoding="UTF-8"?>
> <list xmlns="urn:ietf:params:xml:ns:rlmi" uri="sip:rls_1004 at asterisk.company.com" version="1" fullState="false">
>  <name>rls_1004</name>
>  <resource uri="sip:1001 at asterisk.company.com">
>   <name>Alice</name>
>   <instance id="fldlg" state="active" cid="llhys at asterisk.company.com" />
>  </resource>
>  <resource uri="sip:1002 at asterisk.company.com">
>   <name>Bob</name>
>   <instance id="zyees" state="active" cid="qqhed at asterisk.company.com" />
>  </resource>
> </list>
> --tswyz
> Content-ID: <llhys at asterisk.company.com>
> Content-Type: application/dialog-info+xml
> Content-Length:   236
> <?xml version="1.0" encoding="UTF-8"?>
> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="42" state="full" entity="sip:1001 at asterisk.company.com">
>  <dialog id="1001">
>   <state>terminated</state>
>  </dialog>
> </dialog-info>



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



More information about the asterisk-bugs mailing list