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

[Friendly Automation (JIRA)]

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

Friendly Automation commented on ASTERISK-29961:
------------------------------------------------

Change 18234 merged by Friendly Automation:
res_pjsip_pubsub: RLS 'uri' list attribute mismatch with SUBSCRIBE request

[https://gerrit.asterisk.org/c/asterisk/+/18234|https://gerrit.asterisk.org/c/asterisk/+/18234]

> 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
>            Assignee: 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)