InnovateAsterisk / Browser-Phone

A fully featured browser based WebRTC SIP phone for Asterisk
https://www.innovateasterisk.com
GNU Affero General Public License v3.0
511 stars 252 forks source link

xmpp vcard #271

Open vieridipaola opened 2 years ago

vieridipaola commented 2 years ago

Hi,

Prosody has 2 different vcard modules:

https://prosody.im/doc/modules/mod_vcard4

https://prosody.im/doc/modules/mod_vcard

I believe I should use the second one. In any case, no matter which one I use I still get the following error:

Error in XmppSetMyVcard 
<iq id="559be177-5566-49a3-bc0e-36f97511ecb8" type="error" to="1234@xmpp.mydomain.org/Mri2vvt9" xmlns="jabber:client">

What am I missing?

Does Browser-Phone implement XEP-0292 or XEP-0054 ?

InnovateAsterisk commented 2 years ago

I believe its this one: https://xmpp.org/extensions/xep-0054.html

Do you have any further information on the error, maybe something in the log - It seems to work fine on Openfire.

vieridipaola commented 2 years ago

Do you mean the server log?

I see this in the prosody server log:

c2s55d1cbad62c0 info    Authenticated as 4053@xmpp.mydomain.org
xmpp.mydomain.org:saslauth       debug   sasl reply: <success xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>dj1EYmpGV0ZQZzVwdnBTR1E0ckpKb29sYVZUazA9</success>
c2s55d1cbad62c0 debug   Sending[c2s_unbound]: <success xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
mod_websocket   debug   Websocket received frame: opcode=1, 95 bytes
c2s55d1cbad62c0 debug   Client sent opening <stream:stream> to xmpp.mydomain.org
c2s55d1cbad62c0 debug   Sending[c2s_unbound]: <open xml:lang='en' from='xmpp.mydomain.org' id='3237ce9f-3746-4f38-a417-428176aa49ac' version='1.0' xmlns='urn:ietf:params:xml:ns:xmpp-framing'>
c2s55d1cbad62c0 debug   Sent reply <stream:stream> to client
c2s55d1cbad62c0 debug   Sending[c2s_unbound]: <stream:features>
mod_websocket   debug   Websocket received frame: opcode=1, 108 bytes
c2s55d1cbad62c0 debug   Received[c2s_unbound]: <iq id='_bind_auth_2' type='set'>
rostermanager   debug   load_roster: asked for: 4053@xmpp.mydomain.org
rostermanager   debug   load_roster: loading for new user: 4053@xmpp.mydomain.org
c2s55d1cbad62c0 debug   No legacy vCard to migrate or already migrated
c2s55d1cbad62c0 debug   Sending[c2s]: <iq id='_bind_auth_2' type='result'>
c2s55d1cbad62c0 debug   Resource bound: 4053@xmpp.mydomain.org/EmxSakzY
mod_websocket   debug   Websocket received frame: opcode=1, 117 bytes
c2s55d1cbad62c0 debug   Received[c2s]: <iq id='_session_auth_2' type='set'>
c2s55d1cbad62c0 debug   Sending[c2s]: <iq id='_session_auth_2' type='result' to='4053@xmpp.mydomain.org/EmxSakzY'>
mod_websocket   debug   Websocket received frame: opcode=1, 17133 bytes
c2s55d1cbad62c0 debug   Received[c2s]: <iq id='d53442a6-2317-4427-a77e-da4eadb77bf9' type='set' from='4053@xmpp.mydomain.org/EmxSakzY'>

There's only one line regarding the vCard, and I don't know if that actually triggers the web browser's console error I reported in my first post.