[OpenSIPS-Users] pua_xmpp sip-xmpp gateway - works one way, not other way

mani sivaraman mani.opensips at gmail.com
Wed Jun 24 18:00:34 CEST 2009 

Hi Anca
I did an ngrep of port 5347 to see if jabber server is sending the status
info to c2s interface of opensips. Seems like it is sending some thing like
the personal note "<status>I&apos;m here </status>. in the xml stream from
port 5347. But I don't know if this the correct status since I do not know
xmpp protocol.

But opensips, sends only "presence.winfo" NOTIFY to the sip clients and does
not send any NOTIFY for "presence" event.

Any help to debug the packets is appreciated.

ngrep result:
-------------------

T 172.16.0.139:5347 -> 172.16.0.139:58074 [AP]

  <route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' to='c2s'
from='xmpp.smithmicro.com'><p
  resence xmlns='jabber:client' xmlns:sm='
http://jabberd.jabberstudio.org/ns/session/1.0' from='jabb1 at xm
  pp.smithmicro.com/1fc803228866e0768f8b94199dfbd6b2c2b873b6' to='
jabb2 at xmpp.smithmicro.com/275c37159368
  574be50e07bb5056a2674fb78909' sm:c2s='9'
sm:sm='c4580b9d5dd38f5fd845717e540c4138ee62ac68'><status>I&ap
  os;m here</status><priority>1</priority><c xmlns='
http://jabber.org/protocol/caps' node='http://pidgin
  .im/caps' ver='2.5.7' ext='moodn nickn tunen bob
avatar'/></presence></route>
###



On Wed, Jun 24, 2009 at 9:18 AM, mani sivaraman <mani.opensips at gmail.com>wrote:

> If I sign out sip and xmpp (pidgin) client , all the 3 tables becomes
> empty. After sign in I see the sip clients PIDF in presentity table. and I
> can see data in all the other tables as well. Since the tables are cleaned
> properly after sign out, I guess there is no old data/dates in the tables
> that causes the issue . Sip2XMPP state notification works great. But nothing
> from xmpp to sip. My guess is that Jabberd2 server is not sending any thing
> to opensips. Is there any thing on the Jabberd2 server that I need to check
> ?. I mean how can I make sure the Jabberd2 server is sending the state
> update to opensips ? Is there any setting on Jabberd2 server other than just
> c2s connection via port 5347 ?
>
> mysql> select * from pua;
> Empty set (0.00 sec)
>
> mysql> select * from active_watchers;
> Empty set (0.00 sec)
>
> mysql> select * from presentity;
> Empty set (0.00 sec)
>
> I have sent the opensips debug out in another email for your review.
>
> Thank you
>
>
> On Wed, Jun 24, 2009 at 5:48 AM, Anca Vamanu <anca at opensips.org> wrote:
>
>> Hi Mani,
>>
>> Not, this is not expected. I seems that the jabber server does not send
>> presence information to opensips.
>> I suggest you to start clean ( stop the sever, delete the database dates
>> from tables pua, active_watchers and presentity) and watch the debug
>> messages that say abouth the communication with the jabber server. Watch
>> there is state info is received.
>>
>> regards,
>> Anca
>>
>> mani sivaraman wrote:
>>
>>> Hi Anca
>>> Why is that the NOTIFY received by the SIP Client for the xmpp buddy is
>>> always with no PIDF or xml payload. The Content Length of this NOTIFY is
>>> always 0. Where as the normal sip buddy presence NOTIFY is having the PIDF
>>> xml document. Is this expected ?
>>>
>>> Thanks you
>>> Mani
>>>
>>> On Tue, Jun 23, 2009 at 11:53 AM, mani sivaraman <
>>> mani.opensips at gmail.com <mailto:mani.opensips at gmail.com>> wrote:
>>>
>>>    Hi Anca
>>>    I now switched to opensips from kamailio to make sure I do not
>>>    have too many variables. I'm usingt he exact example config shown
>>>    fir puaxmppConfig on the website. The XMPP client is able to
>>>    detect the presence of sip client, but sip-client is not able to
>>>    get the presence status of the xmpp client. I get some error on
>>>    opensips during execution.
>>>
>>>    You can discard the previous email that uses kamailio.
>>>
>>>    Here is the error I see.
>>>
>>>    Jun 23 11:46:14 [24062] INFO:presence:send_notify_request: NOTIFY
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> via
>>>    sip:msivaraman at 172.16.1.125:6464;transport=udp on behalf of
>>>    sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com> for event presence
>>>    Jun 23 11:46:14 [24060] INFO:presence:send_notify_request: NOTIFY
>>>    sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com> via sip:172.16.0.139:5060
>>>    <http://172.16.0.139:5060> on behalf of
>>>    sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com> for event presence.winfo
>>>    Jun 23 11:47:28 [24062] INFO:presence:send_notify_request: NOTIFY
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> via
>>>    sip:msivaraman at 172.16.1.125:6464;transport=udp on behalf of
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> for event
>>>    presence.winfo
>>>    Jun 23 11:47:28 [24062] INFO:presence:send_notify_request: NOTIFY
>>>    sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com> via sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com> on behalf of
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> for event presence
>>>    Jun 23 11:47:28 [24059] ERROR:pua_xmpp:Notify2Xmpp: 'To' header
>>>    ALREADY PARSED:<sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com>>
>>>    Jun 23 11:47:28 [24059] ERROR:pua_xmpp:Notify2Xmpp: 'From' header
>>>    not parsed
>>>    Jun 23 11:47:37 [24062] INFO:presence:send_notify_request: NOTIFY
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> via
>>>    sip:msivaraman at 172.16.1.125:6464;transport=udp on behalf of
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> for event presence
>>>    Jun 23 11:47:37 [24062] INFO:presence:send_notify_request: NOTIFY
>>>    sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com> via sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com> on behalf of
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> for event presence
>>>    Jun 23 11:47:37 [24061] ERROR:pua_xmpp:Notify2Xmpp: 'To' header
>>>    ALREADY PARSED:<sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com>>
>>>    Jun 23 11:47:37 [24061] ERROR:pua_xmpp:Notify2Xmpp: 'From' header
>>>    not parsed
>>>    Jun 23 11:47:41 [24059] INFO:presence:send_notify_request: NOTIFY
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> via
>>>    sip:msivaraman at 172.16.1.125:6464;transport=udp on behalf of
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> for event presence
>>>    Jun 23 11:47:41 [24059] INFO:presence:send_notify_request: NOTIFY
>>>    sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com> via sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com> on behalf of
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> for event presence
>>>    Jun 23 11:47:41 [24059] ERROR:pua_xmpp:Notify2Xmpp: 'To' header
>>>    ALREADY PARSED:<sip:jabb1*xmpp.smithmicro.com
>>>    <http://xmpp.smithmicro.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com>>
>>>    Jun 23 11:47:41 [24059] ERROR:pua_xmpp:Notify2Xmpp: 'From' header
>>>    not parsed
>>>    Jun 23 11:48:13 [24061] INFO:presence:send_notify_request: NOTIFY
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> via
>>>    sip:msivaraman at 172.16.1.125:6464;transport=udp on behalf of
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> for event
>>>    presence.winfo
>>>    Jun 23 11:48:14 [24062] INFO:presence:send_notify_request: NOTIFY
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> via
>>>    sip:msivaraman at 172.16.1.125:6464;transport=udp on behalf of
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> for event
>>>    presence.winfo
>>>    Jun 23 11:48:14 [24062] INFO:presence:send_notify_request: NOTIFY
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> via
>>>    sip:msivaraman at 172.16.1.125:6464;transport=udp on behalf of
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> for event presence
>>>    Jun 23 11:48:14 [24062] INFO:presence:send_notify_request: NOTIFY
>>>    sip:msivaraman at sips01.smithmicro.com<sip%3Amsivaraman at sips01.smithmicro.com>
>>>    <mailto:sip%3Amsivaraman at sips01.smithmicro.com<sip%253Amsivaraman at sips01.smithmicro.com>>
>>> via
>>>    sip:msivaraman at 172.16.1.125:6464;transport=udp on behalf of
>>>    sip:mani_openfire*dsdev-xmpp.smsi.com
>>>    <http://dsdev-xmpp.smsi.com>@sip-xmpp.smithmicro.com
>>>    <http://sip-xmpp.smithmicro.com> for event presence
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20090624/6aa61e0f/attachment-0001.htm

More information about the Users mailing list