[asterisk-bugs] [JIRA] (ASTERISK-27927) <c ver='asterisk-xmpp'> not XEP-115 conformant

Paul Ina (JIRA) noreply at issues.asterisk.org
Wed Jun 20 08:22:54 CDT 2018


Paul Ina created ASTERISK-27927:
-----------------------------------

             Summary: <c ver='asterisk-xmpp'> not XEP-115 conformant
                 Key: ASTERISK-27927
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27927
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Resources/res_xmpp
    Affects Versions: 15.4.1, 13.18.3
         Environment: Ubuntu 18.04, Asterisk 13.18.3
            Reporter: Paul Ina


The <presence/> stanzas from Asterisk don't conform with XEP-0115 Entity Capabilities. Asterisk always uses 'asterisk-xmpp' as the 'ver' attribute, but XEP-0115 says:

«The 'ver' attribute is a specially-constructed string (called a "verification string") that represents the entity's service discovery identity...»

which would look like this: 

<presence from='romeo at montague.lit/orchard'>
  <c xmlns='http://jabber.org/protocol/caps'
     hash='sha-1'
     node='http://code.google.com/p/exodus'
     ver='QgayPKawpkPSDYmwT/WM94uAlu0='/>
</presence>

This is what Asterisk's res_xmpp does:

<presence  from='phone at example.org/asterisk'>
  <c xmlns='http://jabber.org/protocol/caps'
    node='http://www.asterisk.org/xmpp/client/caps'
    ver='asterisk-xmpp'/>
</presence>

The problem with other XMPP clients is that they often don't recognize Jingle audio and video capabilities with res_xmpp clients. For example I'm unable to call the Asterisk user from aTalk for Android (aTalk version 1.4 has a temporary work-around, but the next version will go back to the standard conformant behaviour).

This is the line in the sources where the 'ver' attribute is set 'asterisk-xmpp', but should be dynamically calculated:
https://github.com/asterisk/asterisk/blob/15.4/res/res_xmpp.c#L2410

I'm running Asterisk 13.18.3, but it looks like all Asterisk versions up to "master" are affected.




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



More information about the asterisk-bugs mailing list