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

2009-07-06 Thread mani sivaraman
I keep getting this error when running pua_xmpp, xmpp and pua module.

Jun 30 12:35:13 [4350] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 30 12:35:13 [4350] ERROR:presence:handle_subscribe: getting stored info
Jun 30 12:35:13 [4351] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 30 12:35:13 [4351] ERROR:presence:handle_subscribe: getting stored info
Jun 30 12:35:13 [4350] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 30 12:35:13 [4350] ERROR:presence:handle_subscribe: getting stored info
Jun 30 12:35:13 [4349] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 30 12:35:13 [4349] ERROR:presence:handle_subscribe: getting stored info

I can see the sip users presence Info being stored in presentity table. I do
not get any presence status info from jabberd2 server to opensips server. I
did a trace on port 5347 and nothing is received when the xmpp user changes
status. However I can see opensips sending the xmpp stanzas and status to
xmpp/jabberd2 server when a sip buddy goes online.offline

Please show me some pointers to look.

On Fri, Jun 26, 2009 at 11:03 AM, mani sivaraman mani.opens...@gmail.comwrote:

 The space is presence only here in the email (due to some formatting
 issue). The cfg file on opensips server does not have any space in between.
 I get presence.winfo NOTIFY. I'm missing only the presence NOTIFY. I see the
 repeated error like this one

 ERROR:presence:get_stored_info: record not found in hash_table
 ERROR:presence:handle_subscribe: getting stored info

 In the below logs, I always see for event presence.winfo, but no for
 event presence. This means that there are is lot of activity for watcher
 Info Subscribe and NOTIFY. But nothing for presence event. Also the method
 pua_xmpp_req_winfo sounds more like this will send subscribe/notify for
 winfo, not for preesnce event. IS there a seperate method to call to request
 subscribe for preesnce event. Or do you call presence subscribe in this same
 function.

 This could be the reason why there are no SUBSCRIBEs or presence NOTIFIEs
 back. Please tell me what this error is, os that I can try to debug this.
 Coudl you do paid support for setting up pua_xmpp module ? Or If you can't
 could you point any one else who can do this. I'm under pressure to complete
 this. Any

 information reg. consultation is appreciated.

 Here is the full debug.

 Listening on
  udp: 172.16.0.139 [172.16.0.139]:5060
 Aliases:
  *: sips01.smithmicro.com:*

 Jun 26 10:41:27 [25843] NOTICE:presence:child_init: init_child [0]  pid
 [25843]
 sips01:/usr/local/etc/opensips# Jun 26 10:42:47 [25845]
 INFO:presence:send_notify_request: NOTIFY sip:jabb1*xmpp.smithm icro.com@
 sip-xmpp.smithmicro.com via
 sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
 sip:rbox...@sip s01.smithmicro.com for event presence
 Jun 26 10:42:47 [25847] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
 PARSED:sip:jabb1*xmpp.smithmicro@sip-xmpp. smithmicro.com
 Jun 26 10:42:47 [25847] ERROR:pua_xmpp:Notify2Xmpp: 'From' header not
 parsed
 Jun 26 10:42:47 [25846] INFO:presence:send_notify_request: NOTIFY
 sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com  via sip:jabb1*
 xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
  event  presence
 Jun 26 10:42:47 [25844] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
 PARSED:sip:jabb1*xmpp.smithmicro@sip-xmpp. smithmicro.com
 Jun 26 10:42:47 [25844] ERROR:pua_xmpp:Notify2Xmpp: 'From' header not
 parsed
 Jun 26 10:43:03 [25847] ERROR:presence:get_stored_info: record not found in
 hash_table
 Jun 26 10:43:03 [25847] ERROR:presence:handle_subscribe: getting stored
 info
 Jun 26 10:43:03 [25846] ERROR:presence:get_stored_info: record not found in
 hash_table
 Jun 26 10:43:03 [25846] ERROR:presence:handle_subscribe: getting stored
 info
 Jun 26 10:43:03 [25847] ERROR:presence:get_stored_info: record not found in
 hash_table
 Jun 26 10:43:03 [25847] ERROR:presence:handle_subscribe: getting stored
 info
 Jun 26 10:43:03 [25844] INFO:presence:send_notify_request: NOTIFY
 sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com  via sip:
 172.16.0.139:5060 on behalf of sip:jabb1*xmpp.smithmicro.com@
 sip-xmpp.smithmicro.com for event presence.winfo
 Jun 26 10:43:03 [25844] INFO:presence:send_notify_request: NOTIFY
 sip:jabb2*xmpp.smithmicro@sip-xmpp.smithmicro.com  via sip:
 172.16.0.139:5060 on behalf of sip:jabb2*xmpp.smithmicro.com@
 sip-xmpp.smithmicro.com for event presence.winfo
 Jun 26 10:43:04 [25845] INFO:presence:send_notify_request: NOTIFY
 sip:jabb2*xmpp.smithmicro@sip-xmpp.smithmicro.com  via
 sip:jabb2*xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
 sip:rbox...@sips01.smithmicro.com sip%3arbox...@sips01.smithmicro.comfor 
 event pre sence
 Jun 26 10:43:04 [25844] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
 

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

2009-06-29 Thread mani sivaraman
The space is presence only here (due to some formatting issue). The cfg file
does not have any space in between. I get presence.winfo NOTIFY. I'm missing
only the presence NOTIFY. I see the repeated error like this one

ERROR:presence:get_stored_info: record not found in hash_table
ERROR:presence:handle_subscribe: getting stored info

This could be the reason why there are no SUBSCRIBEs or presence NOTIFIES
back. Please tell me what this error is, os that I can try to debug this.
Coudl you do paid support for setting up pua_xmpp module ? Or If you can't
could you point any one else who can do this. I'm under pressure to complete
this. Any information reg. consultation is appreciated.


Here is the full debug.



Listening on
 udp: 172.16.0.139 [172.16.0.139]:5060
Aliases:
 *: sips01.smithmicro.com:*

Jun 26 10:41:27 [25841] INFO:core:init_tcp: using epoll_lt as the TCP io
watch method (auto detected)
Jun 26 10:41:27 [25843] NOTICE:core:main: version: opensips 1.5.1-tls
(i386/linux)
Jun 26 10:41:27 [25843] INFO:core:main: using 32 Mb shared memory
Jun 26 10:41:27 [25843] INFO:core:main: using 1 Mb private memory per
process
Jun 26 10:41:27 [25843] NOTICE:signaling:mod_init: initializing module ...
Jun 26 10:41:27 [25843] INFO:sl:mod_init: Initializing StateLess engine
Jun 26 10:41:27 [25843] INFO:tm:mod_init: TM - initializing...
sips01:/usr/local/etc/opensips# Jun 26 10:41:27 [25843]
INFO:maxfwd:mod_init: in
Jun 26 10:41:27 [25843] INFO:usrloc:ul_init_locks: locks array size 512
Jun 26 10:41:27 [25843] INFO:registrar:mod_init: initializing...
Jun 26 10:41:27 [25843] INFO:textops:mod_init: initializing...
Jun 26 10:41:27 [25843] INFO:xlog:mod_init: initializing...
Jun 26 10:41:27 [25843] INFO:acc:mod_init: initializing...
Jun 26 10:41:27 [25843] INFO:auth:mod_init: initializing...
Jun 26 10:41:27 [25843] INFO:auth_db:mod_init: initializing...
Jun 26 10:41:27 [25843] INFO:alias_db:mod_init: initializing...
Jun 26 10:41:27 [25843] NOTICE:presence:mod_init: initializing module ...
Jun 26 10:41:27 [25843] INFO:core:probe_max_receive_buffer: using a UDP
receive
Jun 26 10:41:27 [25844] NOTICE:presence:child_init: init_child [1]  pid
[25844]
Jun 26 10:41:27 [25845] NOTICE:presence:child_init: init_child [2]  pid
[25845]
Jun 26 10:41:27 [25846] NOTICE:presence:child_init: init_child [3]  pid
[25846]
Jun 26 10:41:27 [25847] NOTICE:presence:child_init: init_child [4]  pid
[25847]
Jun 26 10:41:27 [25849] NOTICE:presence:child_init: init_child [-1]  pid
[25849]
Jun 26 10:41:27 [25851] NOTICE:presence:child_init: init_child [-2]  pid
[25851]
Jun 26 10:41:27 [25852] NOTICE:presence:child_init: init_child [5]  pid
[25852]
Jun 26 10:41:27 [25853] NOTICE:presence:child_init: init_child [6]  pid
[25853]
Jun 26 10:41:27 [25854] NOTICE:presence:child_init: init_child [7]  pid
[25854]
Jun 26 10:41:27 [25856] NOTICE:presence:child_init: init_child [8]  pid
[25856]
Jun 26 10:41:27 [25858] NOTICE:presence:child_init: init_child [-4]  pid
[25858]
Jun 26 10:41:27 [25843] NOTICE:presence:child_init: init_child [0]  pid
[25843]
sips01:/usr/local/etc/opensips# Jun 26 10:42:47 [25845]
INFO:presence:send_notify_request: NOTIFY sip:jabb1*xmpp.smithm icro.com@
sip-xmpp.smithmicro.com via sip:jabb1*xmpp.smithmicro.com@
sip-xmpp.smithmicro.com on behalf of sip:rbox...@sip s01.smithmicro.com for
event presence
Jun 26 10:42:47 [25847] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
PARSED:sip:jabb1*xmpp.smithmicro@sip-xmpp. smithmicro.com
Jun 26 10:42:47 [25847] ERROR:pua_xmpp:Notify2Xmpp: 'From' header not parsed
Jun 26 10:42:47 [25846] INFO:presence:send_notify_request: NOTIFY sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com  via sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event  presence
Jun 26 10:42:47 [25844] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
PARSED:sip:jabb1*xmpp.smithmicro@sip-xmpp. smithmicro.com
Jun 26 10:42:47 [25844] ERROR:pua_xmpp:Notify2Xmpp: 'From' header not parsed
Jun 26 10:43:03 [25847] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 26 10:43:03 [25847] ERROR:presence:handle_subscribe: getting stored info
Jun 26 10:43:03 [25846] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 26 10:43:03 [25846] ERROR:presence:handle_subscribe: getting stored info
Jun 26 10:43:03 [25847] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 26 10:43:03 [25847] ERROR:presence:handle_subscribe: getting stored info
Jun 26 10:43:03 [25844] INFO:presence:send_notify_request: NOTIFY sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com  via sip:172.16.0.139:5060 on
behalf of sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com for event
presence.winfo
Jun 26 10:43:03 [25844] INFO:presence:send_notify_request: NOTIFY sip:jabb2*
xmpp.smithmicro@sip-xmpp.smithmicro.com  via sip:172.16.0.139:5060 on
behalf of 

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

2009-06-26 Thread mani sivaraman
The space is presence only here in the email (due to some formatting issue).
The cfg file on opensips server does not have any space in between. I get
presence.winfo NOTIFY. I'm missing only the presence NOTIFY. I see the
repeated error like this one

ERROR:presence:get_stored_info: record not found in hash_table
ERROR:presence:handle_subscribe: getting stored info

In the below logs, I always see for event presence.winfo, but no for
event presence. This means that there are is lot of activity for watcher
Info Subscribe and NOTIFY. But nothing for presence event. Also the method
pua_xmpp_req_winfo sounds more like this will send subscribe/notify for
winfo, not for preesnce event. IS there a seperate method to call to request
subscribe for preesnce event. Or do you call presence subscribe in this same
function.

This could be the reason why there are no SUBSCRIBEs or presence NOTIFIEs
back. Please tell me what this error is, os that I can try to debug this.
Coudl you do paid support for setting up pua_xmpp module ? Or If you can't
could you point any one else who can do this. I'm under pressure to complete
this. Any

information reg. consultation is appreciated.

Here is the full debug.

Listening on
 udp: 172.16.0.139 [172.16.0.139]:5060
Aliases:
 *: sips01.smithmicro.com:*

Jun 26 10:41:27 [25843] NOTICE:presence:child_init: init_child [0]  pid
[25843]
sips01:/usr/local/etc/opensips# Jun 26 10:42:47 [25845]
INFO:presence:send_notify_request: NOTIFY sip:jabb1*xmpp.smithm icro.com@
sip-xmpp.smithmicro.com via
sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
sip:rbox...@sip s01.smithmicro.com for event presence
Jun 26 10:42:47 [25847] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
PARSED:sip:jabb1*xmpp.smithmicro@sip-xmpp. smithmicro.com
Jun 26 10:42:47 [25847] ERROR:pua_xmpp:Notify2Xmpp: 'From' header not parsed
Jun 26 10:42:47 [25846] INFO:presence:send_notify_request: NOTIFY sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com  via sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event  presence
Jun 26 10:42:47 [25844] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
PARSED:sip:jabb1*xmpp.smithmicro@sip-xmpp. smithmicro.com
Jun 26 10:42:47 [25844] ERROR:pua_xmpp:Notify2Xmpp: 'From' header not parsed
Jun 26 10:43:03 [25847] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 26 10:43:03 [25847] ERROR:presence:handle_subscribe: getting stored info
Jun 26 10:43:03 [25846] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 26 10:43:03 [25846] ERROR:presence:handle_subscribe: getting stored info
Jun 26 10:43:03 [25847] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 26 10:43:03 [25847] ERROR:presence:handle_subscribe: getting stored info
Jun 26 10:43:03 [25844] INFO:presence:send_notify_request: NOTIFY sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com  via sip:172.16.0.139:5060 on
behalf of sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com for event
presence.winfo
Jun 26 10:43:03 [25844] INFO:presence:send_notify_request: NOTIFY sip:jabb2*
xmpp.smithmicro@sip-xmpp.smithmicro.com  via sip:172.16.0.139:5060 on
behalf of sip:jabb2*xmpp.smithmicro@sip-xmpp.smithmicro.com for event
presence.winfo
Jun 26 10:43:04 [25845] INFO:presence:send_notify_request: NOTIFY sip:jabb2*
xmpp.smithmicro@sip-xmpp.smithmicro.com  via
sip:jabb2*xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
sip:rbox...@sips01.smithmicro.com sip%3arbox...@sips01.smithmicro.com for
event pre sence
Jun 26 10:43:04 [25844] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
PARSED:sip:jabb2*xmpp.smithmicro@sip-xmpp. smithmicro.com
Jun 26 10:43:04 [25844] ERROR:pua_xmpp:Notify2Xmpp: 'From' header not parsed
Jun 26 10:43:04 [25846] INFO:presence:send_notify_request: NOTIFY sip:jabb2*
xmpp.smithmicro@sip-xmpp.smithmicro.com  via
sip:jabb2*xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event  presence
Jun 26 10:43:04 [25844] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
PARSED:sip:jabb2*xmpp.smithmicro@sip-xmpp. smithmicro.com
Jun 26 10:43:04 [25844] ERROR:pua_xmpp:Notify2Xmpp: 'From' header not parsed
sips01:/usr/local/etc/opensips# Jun 26 10:44:39 [25844]
ERROR:presence:get_stored_info: record not found in hash_table
Jun 26 10:44:39 [25844] ERROR:presence:handle_subscribe: getting stored info
Jun 26 10:44:39 [25847] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 26 10:44:39 [25847] ERROR:presence:handle_subscribe: getting stored info
Jun 26 10:44:39 [25844] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 26 10:44:39 [25844] ERROR:presence:handle_subscribe: getting stored info
Jun 26 10:44:39 [25845] ERROR:presence:get_stored_info: record not found in
hash_table
Jun 26 10:44:39 [25845] 

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

2009-06-25 Thread Anca Vamanu
Hi Mani,

I order to have opensips send subscribe messages to jabber, you need to 
call 'pua_xmpp_req_winfo($ruri, $hdr(Expires));' when you see from 
the script that a Subscribe request is sent to a jabber contact. This is 
the function responsible for sending subscribe messages to jabber.

What opensips version are you using?

regards,
Anca

mani sivaraman wrote:
 Hi Anca
 I do not see any xmpp subscribe packet request sent from opensips to 
 jabber server. That's the reason why jabber server is not sending any 
 presence notify to opensips. Jabber sends the xmpp status to other 
 clients like pidgin.

 When I add a xmpp buddy to sip client, I get the Subscriber/200 OK 
 response. I can see the output saying subscribe sent in behalf of xmpp 
 buddy.. etc. But this is just a sip subscribe output. I do not see any 
 xmpp subscribe sent to jabber server from opensips. What is blocking 
 opensips from sendsing the xmpp subscribes to jabber server ?

 Please let me know.

 On Wed, Jun 24, 2009 at 11:12 AM, mani sivaraman 
 mani.opens...@gmail.com mailto:mani.opens...@gmail.com wrote:

 Oh wait, this xml packet is destined to ja...@xmpp.smithmicro.com
 http://ja...@xmpp.smithmicro.com/275c37159368 , not opensips
 c2s interface. Since all status goes out from 5347 to all xmpp
 clients, I have to separate out the opensips port connected to
 5347 and then try. I found it to be dynamic port 59284. After
 doing ngrep on that port I see opensips sending all status update
 to 5347, but not other way. The only packet from 5347 to 59284 is
 a probe to know if the an offline sip buddy is available (last
 couple of packets)

 Here is the ngrep output

 sips01:/etc/jabberd2# ngrep -d lo port 59284
 interface: lo (127.0.0.0/255.0.0.0 http://127.0.0.0/255.0.0.0)
 filter: (ip or ip6) and ( port 59284 )
 #
 T 172.16.0.139:59284 http://172.16.0.139:59284 -
 172.16.0.139:5347 http://172.16.0.139:5347 [AP]
   presence to=ja...@xmpp.smithmicro.com
 mailto:ja...@xmpp.smithmicro.com
 from=rboxall*sips01.smithmicro.com
 http://sips01.smithmicro.com@xmpp-sip.smithmicro.com
 http://xmpp-sip.smithmicro.com
   type=unavailable/
 ##
 T 172.16.0.139:59284 http://172.16.0.139:59284 -
 172.16.0.139:5347 http://172.16.0.139:5347 [AP]
   presence to=ja...@xmpp.smithmicro.com
 mailto:ja...@xmpp.smithmicro.com
 from=rboxall*sips01.smithmicro.com
 http://sips01.smithmicro.com@xmpp-sip.smithmicro.com
 http://xmpp-sip.smithmicro.com
   type=unavailable/
 ##
 T 172.16.0.139:59284 http://172.16.0.139:59284 -
 172.16.0.139:5347 http://172.16.0.139:5347 [AP]
   presence to=ja...@xmpp.smithmicro.com
 mailto:ja...@xmpp.smithmicro.com
 from=rboxall*sips01.smithmicro.com
 http://sips01.smithmicro.com@xmpp-sip.smithmicro.com
 http://xmpp-sip.smithmicro.com
   .statushi there !!!/status.   
 priority0.00/priority.  /presence
 ##
 T 172.16.0.139:59284 http://172.16.0.139:59284 -
 172.16.0.139:5347 http://172.16.0.139:5347 [AP]
   presence to=ja...@xmpp.smithmicro.com
 mailto:ja...@xmpp.smithmicro.com
 from=rboxall*sips01.smithmicro.com
 http://sips01.smithmicro.com@xmpp-sip.smithmicro.com
 http://xmpp-sip.smithmicro.com
   .statushi there !!!/status.   
 priority0.00/priority.  /presence
 ##
 T 172.16.0.139:5347 http://172.16.0.139:5347 -
 172.16.0.139:59284 http://172.16.0.139:59284 [AP]
   presence xmlns='jabber:client' type='probe'
 to='rboxall*sips01.smithmicro.com
 http://sips01.smithmicro.com@xmpp-sip.smithmicro.com
 http://xmpp-sip.smithmicro.com' from='jabb1
   @xmpp.smithmicro.com http://xmpp.smithmicro.com'/
 ##
 T 172.16.0.139:59284 http://172.16.0.139:59284 -
 172.16.0.139:5347 http://172.16.0.139:5347 [AP]
   presence to=ja...@xmpp.smithmicro.com
 mailto:ja...@xmpp.smithmicro.com
 from=rboxall*sips01.smithmicro.com
 http://sips01.smithmicro.com@xmpp-sip.smithmicro.com
 http://xmpp-sip.smithmicro.com.status
   hi there !!!/status.priority0.00/priority.  /presence
 ##
 T 172.16.0.139:5347 http://172.16.0.139:5347 -
 172.16.0.139:59284 http://172.16.0.139:59284 [AP]
   presence xmlns='jabber:client' type='probe'
 to='msivaraman*sips01.smithmicro.com
 http://sips01.smithmicro.com@xmpp-sip.smithmicro.com
 http://xmpp-sip.smithmicro.com' from='ja
   b...@xmpp.smithmicro.com mailto:b...@xmpp.smithmicro.com'/
 #
 T 172.16.0.139:59284 http://172.16.0.139:59284 -
 172.16.0.139:5347 http://172.16.0.139:5347 [AP]
   presence to=ja...@xmpp.smithmicro.com
 mailto:ja...@xmpp.smithmicro.com
 from=msivaraman*sips01.smithmicro.com
 http://sips01.smithmicro.com@xmpp-sip.smithmicro.com
 http://xmpp-sip.smithmicro.com type=unav
   ailable/




___
Users mailing list

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

2009-06-25 Thread Anca Vamanu
Hi Mani,

I can not open the document on google docs. It says that the document is 
not available.
I see in the paste of your config document that at the line with the 
check before calling pua_xmpp_req_winfo there is a big space in the 
middle of the word presence .. You could check that.

regards,
Anca

mani sivaraman wrote:
 Hi Anca
 I am using 1.5.1 version of opensips and I have pua_xmpp_req_winfo 
 call in my cfg file. I get NOTIFY for Watcher Info with the 
 watcherinfo+xml payoad. But there is no presence state communication 
 sent from Jabber2 server to opensips. Did you look at the debug output 
 document that I sent you ?. That should have it all.

 Here is my config file.


 # main request routing logic

 route{

 # initial sanity checks -- messages with
 # max_forwards==0, or excessively long requests
 if (!mf_process_maxfwd_header(10)) {
 sl_send_reply(483,Too Many Hops);
 exit;
 };

 #if (msg:len =  2048 ) {
 #   sl_send_reply(513, Message too big);
 #   exit;
 #};

 # we record-route all messages -- to make sure that
 # subsequent messages will go through our proxy; that's
 # particularly good if upstream and downstream entities
 # use different transport protocol
 if (!method==REGISTER)
 record_route();

 # subsequent messages withing a dialog should take the
 # path determined by record-routing
 if (loose_route()) {
 # mark routing logic in request
 append_hf(P-hint: rr-enforced\r\n);
 route(1);
 };
 if(method == INVITE)
 setflag(5);

 if( uri=~sip:@sip-xmpp.smithmicro.com 
 mailto:sip%3a@sip-xmpp.smithmicro.com ||
  uri=~sip:@sip-xmpp.smithmicro.com 
 mailto:sip%3a@sip-xmpp.smithmicro.com ||
  uri=~sip:@sips01.smithmicro.com 
 mailto:sip%3a@sips01.smithmicro.com)
 {
 if( is_method(PUBLISH|SUBSCRIBE|NOTIFY))
 route(2);
 }

 if( uri=~sip:@sip-xmpp.smithmicro.com 
 mailto:sip%3a@sip-xmpp.smithmicro.com)
 {
 # absorb retransmissions ###
 if (!t_newtran()) {
 sl_reply_error();
 return;
 }
 if (method == MESSAGE) {
 log(*** xmpp-handled MESSAGE message.\n);
 if (xmpp_send_message()) {
 t_reply(200, Accepted);
 } else {
 t_reply(404, Not found);
 }
 return;
 }else {
 t_reply(403,not supported);
 exit;
 }

 }

 if (!uri==myself) {
 # mark routing logic in request
 append_hf(P-hint: outbound\r\n);
 # if you have some interdomain connections via TLS
 #if(uri=~@tls_domain1.net http://tls_domain1.net) {
 #   t_relay(tls:domain1.net http://domain1.net);
 #   exit;
 #} else if(uri=~@tls_domain2.net 
 http://tls_domain2.net) {
 #   t_relay(tls:domain2.net http://domain2.net);
 #   exit;
 #}
 route(1);
 };

 # if the request is for other domain use UsrLoc
 # (in case, it does not work, use the following command
 # with proper names and addresses in it)
 if (uri==myself) {

 if( is_method(PUBLISH|SUBSCRIBE|NOTIFY))
 route(2);

 if (method==REGISTER) {

 if (!www_authorize(, subscriber))
 {
 www_challenge(, 0);
 exit;
 }

 if (!check_to())
 {
 sl_send_reply(403,Forbidden auth ID);
 exit;
 }

 if (!save(location))
 sl_reply_error();

 exit;
 };

 # native SIP destinations are handled using our USRLOC DB
 if (!lookup(location)) {
 sl_send_reply(404, Not Found);
 exit;
 };
 append_hf(P-hint: usrloc applied\r\n);
 };

 route(1);
 }

 route[1] {
 # send it out now; use stateful forwarding as it works reliably
 # even for UDP2TCP
 if (!t_relay()) {
 sl_reply_error();
 };
 exit;
 }

 route[2]
 {
 if ( 

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

2009-06-24 Thread Anca Vamanu
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.opens...@gmail.com mailto:mani.opens...@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:msivara...@sips01.smithmicro.com
 mailto:sip%3amsivara...@sips01.smithmicro.com via
 sip:msivara...@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:msivara...@sips01.smithmicro.com
 mailto:sip%3amsivara...@sips01.smithmicro.com via
 sip:msivara...@172.16.1.125:6464;transport=udp on behalf of
 sip:msivara...@sips01.smithmicro.com
 mailto:sip%3amsivara...@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:msivara...@sips01.smithmicro.com
 mailto:sip%3amsivara...@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:msivara...@sips01.smithmicro.com
 mailto:sip%3amsivara...@sips01.smithmicro.com via
 sip:msivara...@172.16.1.125:6464;transport=udp on behalf of
 sip:msivara...@sips01.smithmicro.com
 mailto:sip%3amsivara...@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:msivara...@sips01.smithmicro.com
 mailto:sip%3amsivara...@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:msivara...@sips01.smithmicro.com
 mailto:sip%3amsivara...@sips01.smithmicro.com via
 sip:msivara...@172.16.1.125:6464;transport=udp on behalf of
 sip:msivara...@sips01.smithmicro.com
 mailto:sip%3amsivara...@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
 

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

2009-06-24 Thread mani sivaraman
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 statusIapos;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='ja...@xm
  pp.smithmicro.com/1fc803228866e0768f8b94199dfbd6b2c2b873b6' to='
ja...@xmpp.smithmicro.com/275c37159368
  574be50e07bb5056a2674fb78909' sm:c2s='9'
sm:sm='c4580b9d5dd38f5fd845717e540c4138ee62ac68'statusIap
  os;m here/statuspriority1/priorityc 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.opens...@gmail.comwrote:

 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 a...@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.opens...@gmail.com mailto:mani.opens...@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:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.com

 mailto:sip%3amsivara...@sips01.smithmicro.comsip%253amsivara...@sips01.smithmicro.com
 via
sip:msivara...@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:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.com

 mailto:sip%3amsivara...@sips01.smithmicro.comsip%253amsivara...@sips01.smithmicro.com
 via
sip:msivara...@172.16.1.125:6464;transport=udp on behalf of

 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.com

 mailto:sip%3amsivara...@sips01.smithmicro.comsip%253amsivara...@sips01.smithmicro.com
 for event
presence.winfo
Jun 23 11:47:28 [24062] 

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

2009-06-24 Thread mani sivaraman
Oh wait, this xml packet is destined to
ja...@xmpp.smithmicro.comhttp://ja...@xmpp.smithmicro.com/275c37159368
, not opensips c2s interface. Since all status goes out from 5347 to all
xmpp clients, I have to separate out the opensips port connected to 5347 and
then try. I found it to be dynamic port 59284. After doing ngrep on that
port I see opensips sending all status update to 5347, but not other way.
The only packet from 5347 to 59284 is a probe to know if the an offline sip
buddy is available (last couple of packets)

Here is the ngrep output

sips01:/etc/jabberd2# ngrep -d lo port 59284
interface: lo (127.0.0.0/255.0.0.0)
filter: (ip or ip6) and ( port 59284 )
#
T 172.16.0.139:59284 - 172.16.0.139:5347 [AP]
  presence to=ja...@xmpp.smithmicro.com from=rboxall*
sips01.smithmicro@xmpp-sip.smithmicro.com
  type=unavailable/
##
T 172.16.0.139:59284 - 172.16.0.139:5347 [AP]
  presence to=ja...@xmpp.smithmicro.com from=rboxall*
sips01.smithmicro@xmpp-sip.smithmicro.com
  type=unavailable/
##
T 172.16.0.139:59284 - 172.16.0.139:5347 [AP]
  presence to=ja...@xmpp.smithmicro.com from=rboxall*
sips01.smithmicro@xmpp-sip.smithmicro.com
  .statushi there !!!/status.priority0.00/priority.
/presence
##
T 172.16.0.139:59284 - 172.16.0.139:5347 [AP]
  presence to=ja...@xmpp.smithmicro.com from=rboxall*
sips01.smithmicro@xmpp-sip.smithmicro.com
  .statushi there !!!/status.priority0.00/priority.
/presence
##
T 172.16.0.139:5347 - 172.16.0.139:59284 [AP]
  presence xmlns='jabber:client' type='probe' to='rboxall*
sips01.smithmicro@xmpp-sip.smithmicro.com' from='jabb1
  @xmpp.smithmicro.com'/
##
T 172.16.0.139:59284 - 172.16.0.139:5347 [AP]
  presence to=ja...@xmpp.smithmicro.com from=rboxall*
sips01.smithmicro@xmpp-sip.smithmicro.com.status
  hi there !!!/status.priority0.00/priority.  /presence
##
T 172.16.0.139:5347 - 172.16.0.139:59284 [AP]
  presence xmlns='jabber:client' type='probe' to='msivaraman*
sips01.smithmicro@xmpp-sip.smithmicro.com' from='ja
  b...@xmpp.smithmicro.com'/
#
T 172.16.0.139:59284 - 172.16.0.139:5347 [AP]
  presence to=ja...@xmpp.smithmicro.com from=msivaraman*
sips01.smithmicro@xmpp-sip.smithmicro.com type=unav
  ailable/
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


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

2009-06-23 Thread mani sivaraman
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:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
sip:msivara...@172.16.1.125:6464;transport=udp
on behalf of sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com for event
presence
Jun 23 11:46:14 [24060] INFO:presence:send_notify_request: NOTIFY sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com via sip:172.16.0.139:5060 on
behalf of sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com for event
presence.winfo
Jun 23 11:47:28 [24062] INFO:presence:send_notify_request: NOTIFY
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
sip:msivara...@172.16.1.125:6464;transport=udp
on behalf of 
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event presence.winfo
Jun 23 11:47:28 [24062] INFO:presence:send_notify_request: NOTIFY sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com via sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event presence
Jun 23 11:47:28 [24059] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
PARSED:sip:jabb1*xmpp.smithmicro@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:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
sip:msivara...@172.16.1.125:6464;transport=udp
on behalf of 
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event presence
Jun 23 11:47:37 [24062] INFO:presence:send_notify_request: NOTIFY sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com via sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event presence
Jun 23 11:47:37 [24061] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
PARSED:sip:jabb1*xmpp.smithmicro@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:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
sip:msivara...@172.16.1.125:6464;transport=udp
on behalf of 
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event presence
Jun 23 11:47:41 [24059] INFO:presence:send_notify_request: NOTIFY sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com via sip:jabb1*
xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event presence
Jun 23 11:47:41 [24059] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
PARSED:sip:jabb1*xmpp.smithmicro@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:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
sip:msivara...@172.16.1.125:6464;transport=udp
on behalf of 
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event presence.winfo
Jun 23 11:48:14 [24062] INFO:presence:send_notify_request: NOTIFY
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
sip:msivara...@172.16.1.125:6464;transport=udp
on behalf of 
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event presence.winfo
Jun 23 11:48:14 [24062] INFO:presence:send_notify_request: NOTIFY
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
sip:msivara...@172.16.1.125:6464;transport=udp
on behalf of 
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
event presence
Jun 23 11:48:14 [24062] INFO:presence:send_notify_request: NOTIFY
sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
sip:msivara...@172.16.1.125:6464;transport=udp
on behalf of sip:mani_openfire*dsdev-xmpp.smsi@sip-xmpp.smithmicro.comfor
event presence
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


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

2009-06-23 Thread mani sivaraman
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.opens...@gmail.comwrote:

 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:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
  sip:msivara...@172.16.1.125:6464;transport=udp
 on behalf of sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com for
 event presence
 Jun 23 11:46:14 [24060] INFO:presence:send_notify_request: NOTIFY
 sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com via sip:
 172.16.0.139:5060 on behalf of sip:jabb1*xmpp.smithmicro.com@
 sip-xmpp.smithmicro.com for event presence.winfo
 Jun 23 11:47:28 [24062] INFO:presence:send_notify_request: NOTIFY
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
  sip:msivara...@172.16.1.125:6464;transport=udp
 on behalf of 
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
  event presence.winfo
 Jun 23 11:47:28 [24062] INFO:presence:send_notify_request: NOTIFY
 sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com via sip:jabb1*
 xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
  event presence
 Jun 23 11:47:28 [24059] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
 PARSED:sip:jabb1*xmpp.smithmicro@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:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
  sip:msivara...@172.16.1.125:6464;transport=udp
 on behalf of 
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
  event presence
 Jun 23 11:47:37 [24062] INFO:presence:send_notify_request: NOTIFY
 sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com via sip:jabb1*
 xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
  event presence
 Jun 23 11:47:37 [24061] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
 PARSED:sip:jabb1*xmpp.smithmicro@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:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
  sip:msivara...@172.16.1.125:6464;transport=udp
 on behalf of 
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
  event presence
 Jun 23 11:47:41 [24059] INFO:presence:send_notify_request: NOTIFY
 sip:jabb1*xmpp.smithmicro@sip-xmpp.smithmicro.com via sip:jabb1*
 xmpp.smithmicro@sip-xmpp.smithmicro.com on behalf of
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
  event presence
 Jun 23 11:47:41 [24059] ERROR:pua_xmpp:Notify2Xmpp: 'To' header ALREADY
 PARSED:sip:jabb1*xmpp.smithmicro@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:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
  sip:msivara...@172.16.1.125:6464;transport=udp
 on behalf of 
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
  event presence.winfo
 Jun 23 11:48:14 [24062] INFO:presence:send_notify_request: NOTIFY
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
  sip:msivara...@172.16.1.125:6464;transport=udp
 on behalf of 
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
  event presence.winfo
 Jun 23 11:48:14 [24062] INFO:presence:send_notify_request: NOTIFY
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
  sip:msivara...@172.16.1.125:6464;transport=udp
 on behalf of 
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comfor
  event presence
 Jun 23 11:48:14 [24062] INFO:presence:send_notify_request: NOTIFY
 sip:msivara...@sips01.smithmicro.comsip%3amsivara...@sips01.smithmicro.comvia
  sip:msivara...@172.16.1.125:6464;transport=udp
 on behalf of sip:mani_openfire*dsdev-xmpp.smsi@sip-xmpp.smithmicro.comfor 
 event presence