Hi,
I am using SER rel_2_0_0. I am trying to set up a presence server as a simple PA.
I am using xlite UA and when UA registers and subscribes to a particular user presence Event SER doesn't sent a NOTIFY according to the 'time_interval' module parameter. It only responses with the 'immediate NOTIFY' with the closed status tuple. According to my configuration SER should sent a NOTIFY every 15 seconds and it doesn't do it at all. I kindly ask for your feedback.
Below I attached my module configuration and messages exchanged with UA. # -- pa params -- modparam("pa", "default_expires",300) modparam("pa", "max_subscription_expiration", 3600) modparam("pa", "max_publish_expiration", 3600) modparam("pa", "use_db", 1) modparam("pa", "use_callbacks", 1) modparam("pa", "watcherinfo_notify", 0) modparam("pa", "use_offline_winfo", 0) modparam("pa", "offline_winfo_expiration", 259200) modparam("pa", "auth", "none") modparam("pa", "winfo_auth", "implicit") modparam("pa", "pres_rules_file", "presence-rules.xml") modparam("pa", "ignore_408_on_notify", 0) modparam("pa", "timer_interval", 15) modparam("pa", "default_priority_percentage", 0) modparam("pa", "auth_rules_refresh_time", 300) modparam("pa", "async_auth_queries", 1) modparam("pa", "max_auth_requests_per_tick", 600)
# U 2007/06/04 16:52:16.423720 192.168.0.229:7060 -> 192.168.0.165:5160 SUBSCRIBE sip:sen@voip.rd.touk.pl SIP/2.0. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport. Max-Forwards: 70. Contact: sip:hulk@192.168.0.229:7060. To: sip:sen@voip.rd.touk.pl. From: "hulk@voip.rd.touk.pl"sip:hulk@voip.rd.touk.pl;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Accept: multipart/related, application/rlmi+xml, application/pidf+xml. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: X-Lite release 1006e stamp 34025. Event: presence. Content-Length: 0. .
# U 2007/06/04 16:52:16.471312 192.168.0.165:5160 -> 192.168.0.229:7060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport=7060. To: sip:sen@voip.rd.touk.pl;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. From: "hulk@voip.rd.touk.pl"sip:hulk@voip.rd.touk.pl;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Contact: sip:192.168.0.165:5160. Server: Sip EXpress router (2.0.0-rc2 (x86_64/linux)). Content-Length: 0. Warning: 392 192.168.0.165:5160 "Noisy feedback tells: pid=25995 req_src_ip=192.168.0.229 req_src_port=7060 in_uri=sip:sen@voip.rd.touk.pl out_uri=sip:sen@voip.rd.touk.pl via_cnt==1". .
# U 2007/06/04 16:52:16.471328 192.168.0.165:5160 -> 192.168.0.229:7060 NOTIFY sip:hulk@192.168.0.229:7060 SIP/2.0. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. To: "hulk@voip.rd.touk.pl"sip:hulk@voip.rd.touk.pl;tag=8e1a6d2f. From: sip:sen@voip.rd.touk.pl;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. CSeq: 10 NOTIFY. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. Content-Length: 208. User-Agent: Sip EXpress router(2.0.0-rc2 (x86_64/linux)). Max-Forwards: 70. Event: presence. Content-Type: application/pidf+xml;charset="UTF-8". Contact: sip:192.168.0.165:5160. Subscription-State: active;expires=300. . <?xml version="1.0" encoding="UTF-8"?>. <presence xmlns="urn:ietf:params:xml:ns:pidf" entity="pres:sen@voip.rd.touk.pl">. .<tuple id="none">. ..<status><basic>closed</basic></status>. .</tuple>. </presence>.
# U 2007/06/04 16:52:16.572189 192.168.0.229:7060 -> 192.168.0.165:5160 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. Contact: sip:hulk@192.168.0.229:7060. To: "hulk@voip.rd.touk.pl"sip:hulk@voip.rd.touk.pl;tag=8e1a6d2f. From: sip:sen@voip.rd.touk.pl;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 10 NOTIFY. User-Agent: X-Lite release 1006e stamp 34025. Content-Length: 0. . . Cheers TOmasz
Hi Tomasz, the 'timer_interval' parameter specifies the interval after which PA checks changes in the list of presentites (changed presence state, changed/expired subscriptions, ...). If there is a change, NOTIFY corresponding with the change is sent, but if no change found, no NOTIFY is sent. Isn't this your problem?
Vaclav
On Mon, Jun 04, 2007 at 05:02:12PM +0200, tzieleniewski wrote:
Hi,
I am using SER rel_2_0_0. I am trying to set up a presence server as a simple PA.
I am using xlite UA and when UA registers and subscribes to a particular user presence Event SER doesn't sent a NOTIFY according to the 'time_interval' module parameter. It only responses with the 'immediate NOTIFY' with the closed status tuple. According to my configuration SER should sent a NOTIFY every 15 seconds and it doesn't do it at all. I kindly ask for your feedback.
Below I attached my module configuration and messages exchanged with UA. # -- pa params -- modparam("pa", "default_expires",300) modparam("pa", "max_subscription_expiration", 3600) modparam("pa", "max_publish_expiration", 3600) modparam("pa", "use_db", 1) modparam("pa", "use_callbacks", 1) modparam("pa", "watcherinfo_notify", 0) modparam("pa", "use_offline_winfo", 0) modparam("pa", "offline_winfo_expiration", 259200) modparam("pa", "auth", "none") modparam("pa", "winfo_auth", "implicit") modparam("pa", "pres_rules_file", "presence-rules.xml") modparam("pa", "ignore_408_on_notify", 0) modparam("pa", "timer_interval", 15) modparam("pa", "default_priority_percentage", 0) modparam("pa", "auth_rules_refresh_time", 300) modparam("pa", "async_auth_queries", 1) modparam("pa", "max_auth_requests_per_tick", 600)
# U 2007/06/04 16:52:16.423720 192.168.0.229:7060 -> 192.168.0.165:5160 SUBSCRIBE sip:sen@voip.rd.touk.pl SIP/2.0. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport. Max-Forwards: 70. Contact: sip:hulk@192.168.0.229:7060. To: sip:sen@voip.rd.touk.pl. From: "hulk@voip.rd.touk.pl"sip:hulk@voip.rd.touk.pl;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Accept: multipart/related, application/rlmi+xml, application/pidf+xml. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: X-Lite release 1006e stamp 34025. Event: presence. Content-Length: 0. .
# U 2007/06/04 16:52:16.471312 192.168.0.165:5160 -> 192.168.0.229:7060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport=7060. To: sip:sen@voip.rd.touk.pl;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. From: "hulk@voip.rd.touk.pl"sip:hulk@voip.rd.touk.pl;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Contact: sip:192.168.0.165:5160. Server: Sip EXpress router (2.0.0-rc2 (x86_64/linux)). Content-Length: 0. Warning: 392 192.168.0.165:5160 "Noisy feedback tells: pid=25995 req_src_ip=192.168.0.229 req_src_port=7060 in_uri=sip:sen@voip.rd.touk.pl out_uri=sip:sen@voip.rd.touk.pl via_cnt==1". .
# U 2007/06/04 16:52:16.471328 192.168.0.165:5160 -> 192.168.0.229:7060 NOTIFY sip:hulk@192.168.0.229:7060 SIP/2.0. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. To: "hulk@voip.rd.touk.pl"sip:hulk@voip.rd.touk.pl;tag=8e1a6d2f. From: sip:sen@voip.rd.touk.pl;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. CSeq: 10 NOTIFY. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. Content-Length: 208. User-Agent: Sip EXpress router(2.0.0-rc2 (x86_64/linux)). Max-Forwards: 70. Event: presence. Content-Type: application/pidf+xml;charset="UTF-8". Contact: sip:192.168.0.165:5160. Subscription-State: active;expires=300. .
<?xml version="1.0" encoding="UTF-8"?>.
<presence xmlns="urn:ietf:params:xml:ns:pidf" entity="pres:sen@voip.rd.touk.pl">. .<tuple id="none">. ..<status><basic>closed</basic></status>. .</tuple>. </presence>.
# U 2007/06/04 16:52:16.572189 192.168.0.229:7060 -> 192.168.0.165:5160 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. Contact: sip:hulk@192.168.0.229:7060. To: "hulk@voip.rd.touk.pl"sip:hulk@voip.rd.touk.pl;tag=8e1a6d2f. From: sip:sen@voip.rd.touk.pl;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 10 NOTIFY. User-Agent: X-Lite release 1006e stamp 34025. Content-Length: 0. . . Cheers TOmasz
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Yes Tomasz, you are right. The NOTIFY should contain tuple with 'open' status if use_callbacks is set and the presentity is registered. I will look on it...
Vaclav
On Tue, Jun 05, 2007 at 10:24:29AM +0200, TZieleniewski wrote:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Vaclav,<br> <br> Thank you, so that was my misunderstanding of 'time_interval':)<br> But When my UAa subscribes to the presence of another UAb wich is already registered <br> the NOTIFY message contains tuple with the closed state indicated for UAb. <br> Only after the UAb sends PUBLISH message there is an updated NOTIFY sent to UAa with status 'open'.<br> Shouldn't it be like this that if 'auth' module parameter is "none" and the user is registered the NOFITY message for <br> for this user contains tuple with status open??<br> <br> Cheers<br> tomasz<br> <br> Vaclav Kubart pisze: <blockquote cite="mid:20070605074149.GE3832@vencore.sip-server.net" type="cite"> <pre wrap="">Hi Tomasz, the 'timer_interval' parameter specifies the interval after which PA checks changes in the list of presentites (changed presence state, changed/expired subscriptions, ...). If there is a change, NOTIFY corresponding with the change is sent, but if no change found, no NOTIFY is sent. Isn't this your problem?
VaclavOn Mon, Jun 04, 2007 at 05:02:12PM +0200, tzieleniewski wrote: </pre>
<blockquote type="cite"> <pre wrap="">Hi,
I am using SER rel_2_0_0. I am trying to set up a presence server as a simple PA.
I am using xlite UA and when UA registers and subscribes to a particular user presence Event SER doesn't sent a NOTIFY according to the 'time_interval' module parameter. It only responses with the 'immediate NOTIFY' with the closed status tuple. According to my configuration SER should sent a NOTIFY every 15 seconds and it doesn't do it at all. I kindly ask for your feedback.
Below I attached my module configuration and messages exchanged with UA. # -- pa params -- modparam("pa", "default_expires",300) modparam("pa", "max_subscription_expiration", 3600) modparam("pa", "max_publish_expiration", 3600) modparam("pa", "use_db", 1) modparam("pa", "use_callbacks", 1) modparam("pa", "watcherinfo_notify", 0) modparam("pa", "use_offline_winfo", 0) modparam("pa", "offline_winfo_expiration", 259200) modparam("pa", "auth", "none") modparam("pa", "winfo_auth", "implicit") modparam("pa", "pres_rules_file", "presence-rules.xml") modparam("pa", "ignore_408_on_notify", 0) modparam("pa", "timer_interval", 15) modparam("pa", "default_priority_percentage", 0) modparam("pa", "auth_rules_refresh_time", 300) modparam("pa", "async_auth_queries", 1) modparam("pa", "max_auth_requests_per_tick", 600)
# U 2007/06/04 16:52:16.423720 192.168.0.229:7060 -> 192.168.0.165:5160 SUBSCRIBE <a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a> SIP/2.0. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport. Max-Forwards: 70. Contact: <a class="moz-txt-link-rfc2396E" href="sip:hulk@192.168.0.229:7060"><sip:hulk@192.168.0.229:7060></a>. To: <a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl"><sip:sen@voip.rd.touk.pl></a>. From: <a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a><a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl"><sip:hulk@voip.rd.touk.pl></a>;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Accept: multipart/related, application/rlmi+xml, application/pidf+xml. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: X-Lite release 1006e stamp 34025. Event: presence. Content-Length: 0. .
# U 2007/06/04 16:52:16.471312 192.168.0.165:5160 -> 192.168.0.229:7060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport=7060. To: <a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl"><sip:sen@voip.rd.touk.pl></a>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. From: <a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a><a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl"><sip:hulk@voip.rd.touk.pl></a>;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Contact: <a class="moz-txt-link-rfc2396E" href="sip:192.168.0.165:5160"><sip:192.168.0.165:5160></a>. Server: Sip EXpress router (2.0.0-rc2 (x86_64/linux)). Content-Length: 0. Warning: 392 192.168.0.165:5160 "Noisy feedback tells: pid=25995 req_src_ip=192.168.0.229 req_src_port=7060 in_uri=<a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a> out_uri=<a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a> via_cnt==1". .
# U 2007/06/04 16:52:16.471328 192.168.0.165:5160 -> 192.168.0.229:7060 NOTIFY <a class="moz-txt-link-freetext" href="sip:hulk@192.168.0.229:7060">sip:hulk@192.168.0.229:7060</a> SIP/2.0. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. To: <a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a><a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl"><sip:hulk@voip.rd.touk.pl></a>;tag=8e1a6d2f. From: <a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl"><sip:sen@voip.rd.touk.pl></a>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. CSeq: 10 NOTIFY. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. Content-Length: 208. User-Agent: Sip EXpress router(2.0.0-rc2 (x86_64/linux)). Max-Forwards: 70. Event: presence. Content-Type: application/pidf+xml;charset="UTF-8". Contact: <a class="moz-txt-link-rfc2396E" href="sip:192.168.0.165:5160"><sip:192.168.0.165:5160></a>. Subscription-State: active;expires=300. . <?xml version="1.0" encoding="UTF-8"?>. <presence xmlns="urn:ietf:params:<a class="moz-txt-link-freetext" href="xml:ns:pidf">xml:ns:pidf</a>" entity=<a class="moz-txt-link-rfc2396E" href="pres:sen@voip.rd.touk.pl">"pres:sen@voip.rd.touk.pl"</a>>. .<tuple id="none">. ..<status><basic>closed</basic></status>. .</tuple>. </presence>.
# U 2007/06/04 16:52:16.572189 192.168.0.229:7060 -> 192.168.0.165:5160 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. Contact: <a class="moz-txt-link-rfc2396E" href="sip:hulk@192.168.0.229:7060"><sip:hulk@192.168.0.229:7060></a>. To: <a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a><a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl"><sip:hulk@voip.rd.touk.pl></a>;tag=8e1a6d2f. From: <a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl"><sip:sen@voip.rd.touk.pl></a>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 10 NOTIFY. User-Agent: X-Lite release 1006e stamp 34025. Content-Length: 0. . . Cheers TOmasz
Serusers mailing list <a class="moz-txt-link-abbreviated" href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a> <a class="moz-txt-link-freetext" href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a> </pre>
</blockquote> <pre wrap=""><!----> </pre> </blockquote> <br> </body> </html>
So, I tried it and it works for me...
Are you using domain (domain -> did) + uri_db (username + did -> uid) modules?
Vaclav
On Tue, Jun 05, 2007 at 02:57:34PM +0200, Vaclav Kubart wrote:
Yes Tomasz, you are right. The NOTIFY should contain tuple with 'open' status if use_callbacks is set and the presentity is registered. I will look on it...
VaclavOn Tue, Jun 05, 2007 at 10:24:29AM +0200, TZieleniewski wrote:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Vaclav,<br> <br> Thank you, so that was my misunderstanding of 'time_interval':)<br> But When my UAa subscribes to the presence of another UAb wich is already registered <br> the NOTIFY message contains tuple with the closed state indicated for UAb. <br> Only after the UAb sends PUBLISH message there is an updated NOTIFY sent to UAa with status 'open'.<br> Shouldn't it be like this that if 'auth' module parameter is "none" and the user is registered the NOFITY message for <br> for this user contains tuple with status open??<br> <br> Cheers<br> tomasz<br> <br> Vaclav Kubart pisze: <blockquote cite="mid:20070605074149.GE3832@vencore.sip-server.net" type="cite"> <pre wrap="">Hi Tomasz, the 'timer_interval' parameter specifies the interval after which PA checks changes in the list of presentites (changed presence state, changed/expired subscriptions, ...). If there is a change, NOTIFY corresponding with the change is sent, but if no change found, no NOTIFY is sent. Isn't this your problem?
VaclavOn Mon, Jun 04, 2007 at 05:02:12PM +0200, tzieleniewski wrote: </pre>
<blockquote type="cite"> <pre wrap="">Hi,
I am using SER rel_2_0_0. I am trying to set up a presence server as a simple PA.
I am using xlite UA and when UA registers and subscribes to a particular user presence Event SER doesn't sent a NOTIFY according to the 'time_interval' module parameter. It only responses with the 'immediate NOTIFY' with the closed status tuple. According to my configuration SER should sent a NOTIFY every 15 seconds and it doesn't do it at all. I kindly ask for your feedback.
Below I attached my module configuration and messages exchanged with UA. # -- pa params -- modparam("pa", "default_expires",300) modparam("pa", "max_subscription_expiration", 3600) modparam("pa", "max_publish_expiration", 3600) modparam("pa", "use_db", 1) modparam("pa", "use_callbacks", 1) modparam("pa", "watcherinfo_notify", 0) modparam("pa", "use_offline_winfo", 0) modparam("pa", "offline_winfo_expiration", 259200) modparam("pa", "auth", "none") modparam("pa", "winfo_auth", "implicit") modparam("pa", "pres_rules_file", "presence-rules.xml") modparam("pa", "ignore_408_on_notify", 0) modparam("pa", "timer_interval", 15) modparam("pa", "default_priority_percentage", 0) modparam("pa", "auth_rules_refresh_time", 300) modparam("pa", "async_auth_queries", 1) modparam("pa", "max_auth_requests_per_tick", 600)
# U 2007/06/04 16:52:16.423720 192.168.0.229:7060 -> 192.168.0.165:5160 SUBSCRIBE <a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a> SIP/2.0. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport. Max-Forwards: 70. Contact: <a class="moz-txt-link-rfc2396E" href="sip:hulk@192.168.0.229:7060"><sip:hulk@192.168.0.229:7060></a>. To: <a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl"><sip:sen@voip.rd.touk.pl></a>. From: <a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a><a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl"><sip:hulk@voip.rd.touk.pl></a>;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Accept: multipart/related, application/rlmi+xml, application/pidf+xml. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: X-Lite release 1006e stamp 34025. Event: presence. Content-Length: 0. .
# U 2007/06/04 16:52:16.471312 192.168.0.165:5160 -> 192.168.0.229:7060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport=7060. To: <a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl"><sip:sen@voip.rd.touk.pl></a>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. From: <a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a><a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl"><sip:hulk@voip.rd.touk.pl></a>;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Contact: <a class="moz-txt-link-rfc2396E" href="sip:192.168.0.165:5160"><sip:192.168.0.165:5160></a>. Server: Sip EXpress router (2.0.0-rc2 (x86_64/linux)). Content-Length: 0. Warning: 392 192.168.0.165:5160 "Noisy feedback tells: pid=25995 req_src_ip=192.168.0.229 req_src_port=7060 in_uri=<a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a> out_uri=<a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a> via_cnt==1". .
# U 2007/06/04 16:52:16.471328 192.168.0.165:5160 -> 192.168.0.229:7060 NOTIFY <a class="moz-txt-link-freetext" href="sip:hulk@192.168.0.229:7060">sip:hulk@192.168.0.229:7060</a> SIP/2.0. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. To: <a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a><a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl"><sip:hulk@voip.rd.touk.pl></a>;tag=8e1a6d2f. From: <a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl"><sip:sen@voip.rd.touk.pl></a>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. CSeq: 10 NOTIFY. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. Content-Length: 208. User-Agent: Sip EXpress router(2.0.0-rc2 (x86_64/linux)). Max-Forwards: 70. Event: presence. Content-Type: application/pidf+xml;charset="UTF-8". Contact: <a class="moz-txt-link-rfc2396E" href="sip:192.168.0.165:5160"><sip:192.168.0.165:5160></a>. Subscription-State: active;expires=300. . <?xml version="1.0" encoding="UTF-8"?>. <presence xmlns="urn:ietf:params:<a class="moz-txt-link-freetext" href="xml:ns:pidf">xml:ns:pidf</a>" entity=<a class="moz-txt-link-rfc2396E" href="pres:sen@voip.rd.touk.pl">"pres:sen@voip.rd.touk.pl"</a>>. .<tuple id="none">. ..<status><basic>closed</basic></status>. .</tuple>. </presence>.
# U 2007/06/04 16:52:16.572189 192.168.0.229:7060 -> 192.168.0.165:5160 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. Contact: <a class="moz-txt-link-rfc2396E" href="sip:hulk@192.168.0.229:7060"><sip:hulk@192.168.0.229:7060></a>. To: <a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a><a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl"><sip:hulk@voip.rd.touk.pl></a>;tag=8e1a6d2f. From: <a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl"><sip:sen@voip.rd.touk.pl></a>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 10 NOTIFY. User-Agent: X-Lite release 1006e stamp 34025. Content-Length: 0. . . Cheers TOmasz
Serusers mailing list <a class="moz-txt-link-abbreviated" href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a> <a class="moz-txt-link-freetext" href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a> </pre>
</blockquote> <pre wrap=""><!----> </pre> </blockquote> <br> </body> </html>
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I meant using lookup_domain and lookup_user functions in the script. Vaclav
On Wed, Jun 06, 2007 at 09:37:29PM +0200, TZieleniewski wrote:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Vaclav where should I use those modules?<br> Could you be please more precise:)<br> you mean to load those modules or use them in some specific way in the context pf presence??<br> <br> Thank you<br> Cheers tomasz<br> <br> Vaclav Kubart pisze: <blockquote cite="mid:20070605155449.GK3832@vencore.sip-server.net" type="cite"> <pre wrap="">So, I tried it and it works for me...
Are you using domain (domain -> did) + uri_db (username + did -> uid) modules?
VaclavOn Tue, Jun 05, 2007 at 02:57:34PM +0200, Vaclav Kubart wrote: </pre>
<blockquote type="cite"> <pre wrap="">Yes Tomasz, you are right. The NOTIFY should contain tuple with 'open' status if use_callbacks is set and the presentity is registered. I will look on it...
VaclavOn Tue, Jun 05, 2007 at 10:24:29AM +0200, TZieleniewski wrote: </pre> <blockquote type="cite"> <pre wrap=""><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Vaclav,<br> <br> Thank you, so that was my misunderstanding of 'time_interval':)<br> But When my UAa subscribes to the presence of another UAb wich is already registered <br> the NOTIFY message contains tuple with the closed state indicated for UAb. <br> Only after the UAb sends PUBLISH message there is an updated NOTIFY sent to UAa with status 'open'.<br> Shouldn't it be like this that if 'auth' module parameter is "none" and the user is registered the NOFITY message for <br> for this user contains tuple with status open??<br> <br> Cheers<br> tomasz<br> <br> Vaclav Kubart pisze: <blockquote cite=<a class="moz-txt-link-rfc2396E" href="mailto:mid:20070605074149.GE3832@vencore.sip-server.net">"mid:20070605074149.GE3832@vencore.sip-server.net"</a> type="cite"> <pre wrap="">Hi Tomasz, the 'timer_interval' parameter specifies the interval after which PA checks changes in the list of presentites (changed presence state, changed/expired subscriptions, ...). If there is a change, NOTIFY corresponding with the change is sent, but if no change found, no NOTIFY is sent. Isn't this your problem?
VaclavOn Mon, Jun 04, 2007 at 05:02:12PM +0200, tzieleniewski wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi,
I am using SER rel_2_0_0. I am trying to set up a presence server as a simple PA.
I am using xlite UA and when UA registers and subscribes to a particular user presence Event SER doesn't sent a NOTIFY according to the 'time_interval' module parameter. It only responses with the 'immediate NOTIFY' with the closed status tuple. According to my configuration SER should sent a NOTIFY every 15 seconds and it doesn't do it at all. I kindly ask for your feedback.
Below I attached my module configuration and messages exchanged with UA. # -- pa params -- modparam("pa", "default_expires",300) modparam("pa", "max_subscription_expiration", 3600) modparam("pa", "max_publish_expiration", 3600) modparam("pa", "use_db", 1) modparam("pa", "use_callbacks", 1) modparam("pa", "watcherinfo_notify", 0) modparam("pa", "use_offline_winfo", 0) modparam("pa", "offline_winfo_expiration", 259200) modparam("pa", "auth", "none") modparam("pa", "winfo_auth", "implicit") modparam("pa", "pres_rules_file", "presence-rules.xml") modparam("pa", "ignore_408_on_notify", 0) modparam("pa", "timer_interval", 15) modparam("pa", "default_priority_percentage", 0) modparam("pa", "auth_rules_refresh_time", 300) modparam("pa", "async_auth_queries", 1) modparam("pa", "max_auth_requests_per_tick", 600)
# U 2007/06/04 16:52:16.423720 192.168.0.229:7060 -&gt; 192.168.0.165:5160 SUBSCRIBE <a class="moz-txt-link-freetext" href=<a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl">"sip:sen@voip.rd.touk.pl"</a>><a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a></a> SIP/2.0. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport. Max-Forwards: 70. Contact: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:hulk@192.168.0.229:7060">"sip:hulk@192.168.0.229:7060"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:hulk@192.168.0.229:7060>">sip:hulk@192.168.0.229:7060&gt</a>;</a>. To: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl">"sip:sen@voip.rd.touk.pl"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl>">sip:sen@voip.rd.touk.pl&gt</a>;</a>. From: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"mailto:hulk@voip.rd.touk.pl"</a>><a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a></a><a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl">"sip:hulk@voip.rd.touk.pl"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:hulk@voip.rd.touk.pl>">sip:hulk@voip.rd.touk.pl&gt</a>;</a>;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Accept: multipart/related, application/rlmi+xml, application/pidf+xml. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: X-Lite release 1006e stamp 34025. Event: presence. Content-Length: 0. .
# U 2007/06/04 16:52:16.471312 192.168.0.165:5160 -&gt; 192.168.0.229:7060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport=7060. To: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl">"sip:sen@voip.rd.touk.pl"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl>">sip:sen@voip.rd.touk.pl&gt</a>;</a>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. From: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"mailto:hulk@voip.rd.touk.pl"</a>><a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a></a><a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl">"sip:hulk@voip.rd.touk.pl"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:hulk@voip.rd.touk.pl>">sip:hulk@voip.rd.touk.pl&gt</a>;</a>;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Contact: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:192.168.0.165:5160">"sip:192.168.0.165:5160"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:192.168.0.165:5160>">sip:192.168.0.165:5160&gt</a>;</a>. Server: Sip EXpress router (2.0.0-rc2 (x86_64/linux)). Content-Length: 0. Warning: 392 192.168.0.165:5160 "Noisy feedback tells: pid=25995 req_src_ip=192.168.0.229 req_src_port=7060 in_uri=<a class="moz-txt-link-freetext" href=<a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl">"sip:sen@voip.rd.touk.pl"</a>><a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a></a> out_uri=<a class="moz-txt-link-freetext" href=<a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl">"sip:sen@voip.rd.touk.pl"</a>><a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a></a> via_cnt==1". .
# U 2007/06/04 16:52:16.471328 192.168.0.165:5160 -&gt; 192.168.0.229:7060 NOTIFY <a class="moz-txt-link-freetext" href=<a class="moz-txt-link-rfc2396E" href="sip:hulk@192.168.0.229:7060">"sip:hulk@192.168.0.229:7060"</a>><a class="moz-txt-link-freetext" href="sip:hulk@192.168.0.229:7060">sip:hulk@192.168.0.229:7060</a></a> SIP/2.0. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. To: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"mailto:hulk@voip.rd.touk.pl"</a>><a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a></a><a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl">"sip:hulk@voip.rd.touk.pl"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:hulk@voip.rd.touk.pl>">sip:hulk@voip.rd.touk.pl&gt</a>;</a>;tag=8e1a6d2f. From: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl">"sip:sen@voip.rd.touk.pl"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl>">sip:sen@voip.rd.touk.pl&gt</a>;</a>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. CSeq: 10 NOTIFY. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. Content-Length: 208. User-Agent: Sip EXpress router(2.0.0-rc2 (x86_64/linux)). Max-Forwards: 70. Event: presence. Content-Type: application/pidf+xml;charset="UTF-8". Contact: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:192.168.0.165:5160">"sip:192.168.0.165:5160"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:192.168.0.165:5160>">sip:192.168.0.165:5160&gt</a>;</a>. Subscription-State: active;expires=300. . &lt;?xml version="1.0" encoding="UTF-8"?&gt;. &lt;presence xmlns="urn:ietf:params:<a class="moz-txt-link-freetext" href=<a class="moz-txt-link-rfc2396E" href="xml:ns:pidf">"xml:ns:pidf"</a>><a class="moz-txt-link-freetext" href="xml:ns:pidf">xml:ns:pidf</a></a>" entity=<a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="pres:sen@voip.rd.touk.pl">"pres:sen@voip.rd.touk.pl"</a>><a class="moz-txt-link-rfc2396E" href="pres:sen@voip.rd.touk.pl">"pres:sen@voip.rd.touk.pl"</a></a>&gt;. .&lt;tuple id="none"&gt;. ..&lt;status&gt;&lt;basic&gt;closed&lt;/basic&gt;&lt;/status&gt;. .&lt;/tuple&gt;. &lt;/presence&gt;.
# U 2007/06/04 16:52:16.572189 192.168.0.229:7060 -&gt; 192.168.0.165:5160 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. Contact: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:hulk@192.168.0.229:7060">"sip:hulk@192.168.0.229:7060"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:hulk@192.168.0.229:7060>">sip:hulk@192.168.0.229:7060&gt</a>;</a>. To: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"mailto:hulk@voip.rd.touk.pl"</a>><a class="moz-txt-link-rfc2396E" href="mailto:hulk@voip.rd.touk.pl">"hulk@voip.rd.touk.pl"</a></a><a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:hulk@voip.rd.touk.pl">"sip:hulk@voip.rd.touk.pl"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:hulk@voip.rd.touk.pl>">sip:hulk@voip.rd.touk.pl&gt</a>;</a>;tag=8e1a6d2f. From: <a class="moz-txt-link-rfc2396E" href=<a class="moz-txt-link-rfc2396E" href="sip:sen@voip.rd.touk.pl">"sip:sen@voip.rd.touk.pl"</a>>&lt;<a class="moz-txt-link-freetext" href="sip:sen@voip.rd.touk.pl>">sip:sen@voip.rd.touk.pl&gt</a>;</a>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 10 NOTIFY. User-Agent: X-Lite release 1006e stamp 34025. Content-Length: 0. . . Cheers TOmasz
Serusers mailing list <a class="moz-txt-link-abbreviated" href=<a class="moz-txt-link-rfc2396E" href="mailto:Serusers@lists.iptel.org">"mailto:Serusers@lists.iptel.org"</a>><a class="moz-txt-link-abbreviated" href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a></a> <a class="moz-txt-link-freetext" href=<a class="moz-txt-link-rfc2396E" href="http://lists.iptel.org/mailman/listinfo/serusers">"http://lists.iptel.org/mailman/listinfo/serusers"</a>><a class="moz-txt-link-freetext" href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a></a> </pre> </blockquote> <pre wrap=""><!----> </pre> </blockquote> <br> </body> </html> </pre> </blockquote> <pre wrap="">_______________________________________________ Serusers mailing list <a class="moz-txt-link-abbreviated" href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a> <a class="moz-txt-link-freetext" href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a> </pre>
</blockquote> <pre wrap=""><!----> </pre> </blockquote> <br> </body> </html>
Hi Vaclav,
Thank you for help everything works fine now. I missed the lookup_user function and didn't have and uid avp loaded before the handle_*() method.
Cheers tomasz
I meant using lookup_domain and lookup_user functions in the script. Vaclav
On Wed, Jun 06, 2007 at 09:37:29PM +0200, TZieleniewski wrote:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Vaclav where should I use those modules?<br> Could you be please more precise:)<br> you mean to load those modules or use them in some specific way in the context pf presence??<br> <br> Thank you<br> Cheers tomasz<br> <br> Vaclav Kubart pisze: <blockquote cite="mid:20070605155449.GK3832@vencore.sip-server.net" type="cite"> <pre wrap="">So, I tried it and it works for me...
Are you using domain (domain -> did) + uri_db (username + did -> uid) modules?
VaclavOn Tue, Jun 05, 2007 at 02:57:34PM +0200, Vaclav Kubart wrote: </pre>
<blockquote type="cite"> <pre wrap="">Yes Tomasz, you are right. The NOTIFY should contain tuple with 'open' status if use_callbacks is set and the presentity is registered. I will look on it...
VaclavOn Tue, Jun 05, 2007 at 10:24:29AM +0200, TZieleniewski wrote: </pre> <blockquote type="cite"> <pre wrap=""><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Vaclav,<br> <br> Thank you, so that was my misunderstanding of 'time_interval':)<br> But When my UAa subscribes to the presence of another UAb wich is already registered <br> the NOTIFY message contains tuple with the closed state indicated for UAb. <br> Only after the UAb sends PUBLISH message there is an updated NOTIFY sent to UAa with status 'open'.<br> Shouldn't it be like this that if 'auth' module parameter is "none" and the user is registered the NOFITY message for <br> for this user contains tuple with status open??<br> <br> Cheers<br> tomasz<br> <br> Vaclav Kubart pisze: <blockquote cite=<a class="moz-txt-link-rfc2396E" href="mailto:mid:20070605074149.GE3832@vencore.sip-server.net">"mid:20070605074149.GE3832@vencore.sip-server.net"</a> type="cite"> <pre wrap="">Hi Tomasz, the 'timer_interval' parameter specifies the interval after which PA checks changes in the list of presentites (changed presence state, changed/expired subscriptions, ...). If there is a change, NOTIFY corresponding with the change is sent, but if no change found, no NOTIFY is sent. Isn't this your problem?
VaclavOn Mon, Jun 04, 2007 at 05:02:12PM +0200, tzieleniewski wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi,
I am using SER rel_2_0_0. I am trying to set up a presence server as a simple PA.
I am using xlite UA and when UA registers and subscribes to a particular user presence Event SER doesn't sent a NOTIFY according to the 'time_interval' module parameter. It only responses with the 'immediate NOTIFY' with the closed status tuple. According to my configuration SER should sent a NOTIFY every 15 seconds and it doesn't do it at all. I kindly ask for your feedback.
Below I attached my module configuration and messages exchanged with UA. # -- pa params -- modparam("pa", "default_expires",300) modparam("pa", "max_subscription_expiration", 3600) modparam("pa", "max_publish_expiration", 3600) modparam("pa", "use_db", 1) modparam("pa", "use_callbacks", 1) modparam("pa", "watcherinfo_notify", 0) modparam("pa", "use_offline_winfo", 0) modparam("pa", "offline_winfo_expiration", 259200) modparam("pa", "auth", "none") modparam("pa", "winfo_auth", "implicit") modparam("pa", "pres_rules_file", "presence-rules.xml") modparam("pa", "ignore_408_on_notify", 0) modparam("pa", "timer_inte
Hi Tomasz, you are welcome. :-)
Did you call 'lookup_user' before 'save' function? I.e. registrar used UIDs but PA not?
It should work if neither registrar nor PA use UIDs or if both registrar and PA use UIDs. But if one of them uses UID and the other one not, it should NOT work...
Vaclav
On Mon, Jun 11, 2007 at 09:48:10AM +0200, tzieleniewski wrote:
Hi Vaclav,
Thank you for help everything works fine now. I missed the lookup_user function and didn't have and uid avp loaded before the handle_*() method.
Cheers tomasz
I meant using lookup_domain and lookup_user functions in the script. Vaclav
On Wed, Jun 06, 2007 at 09:37:29PM +0200, TZieleniewski wrote:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Vaclav where should I use those modules?<br> Could you be please more precise:)<br> you mean to load those modules or use them in some specific way in the context pf presence??<br> <br> Thank you<br> Cheers tomasz<br> <br> Vaclav Kubart pisze: <blockquote cite="mid:20070605155449.GK3832@vencore.sip-server.net" type="cite"> <pre wrap="">So, I tried it and it works for me...
Are you using domain (domain -> did) + uri_db (username + did -> uid) modules?
VaclavOn Tue, Jun 05, 2007 at 02:57:34PM +0200, Vaclav Kubart wrote: </pre>
<blockquote type="cite"> <pre wrap="">Yes Tomasz, you are right. The NOTIFY should contain tuple with 'open' status if use_callbacks is set and the presentity is registered. I will look on it...
VaclavOn Tue, Jun 05, 2007 at 10:24:29AM +0200, TZieleniewski wrote: </pre> <blockquote type="cite"> <pre wrap=""><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Vaclav,<br> <br> Thank you, so that was my misunderstanding of 'time_interval':)<br> But When my UAa subscribes to the presence of another UAb wich is already registered <br> the NOTIFY message contains tuple with the closed state indicated for UAb. <br> Only after the UAb sends PUBLISH message there is an updated NOTIFY sent to UAa with status 'open'.<br> Shouldn't it be like this that if 'auth' module parameter is "none" and the user is registered the NOFITY message for <br> for this user contains tuple with status open??<br> <br> Cheers<br> tomasz<br> <br> Vaclav Kubart pisze: <blockquote cite=<a class="moz-txt-link-rfc2396E" href="mailto:mid:20070605074149.GE3832@vencore.sip-server.net">"mid:20070605074149.GE3832@vencore.sip-server.net"</a> type="cite"> <pre wrap="">Hi Tomasz, the 'timer_interval' parameter specifies the interval after which PA checks changes in the list of presentites (changed presence state, changed/expired subscriptions, ...). If there is a change, NOTIFY corresponding with the change is sent, but if no change found, no NOTIFY is sent. Isn't this your problem?
VaclavOn Mon, Jun 04, 2007 at 05:02:12PM +0200, tzieleniewski wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi,
I am using SER rel_2_0_0. I am trying to set up a presence server as a simple PA.
I am using xlite UA and when UA registers and subscribes to a particular user presence Event SER doesn't sent a NOTIFY according to the 'time_interval' module parameter. It only responses with the 'immediate NOTIFY' with the closed status tuple. According to my configuration SER should sent a NOTIFY every 15 seconds and it doesn't do it at all. I kindly ask for your feedback.
Below I attached my module configuration and messages exchanged with UA. # -- pa params -- modparam("pa", "default_expires",300) modparam("pa", "max_subscription_expiration", 3600) modparam("pa", "max_publish_expiration", 3600) modparam("pa", "use_db", 1) modparam("pa", "use_callbacks", 1) modparam("pa", "watcherinfo_notify", 0) modparam("pa", "use_offline_winfo", 0) modparam("pa", "offline_winfo_expiration", 259200) modparam("pa", "auth", "none") modparam("pa", "winfo_auth", "implicit") modparam("pa", "pres_rules_file", "presence-rules.xml") modparam("pa", "ignore_408_on_notify", 0) modparam("pa", "timer_inte
Hi Tomasz, you are welcome. :-)
Did you call 'lookup_user' before 'save' function? I.e. registrar used UIDs but PA not?
Yes exactly, when I handle register I first call lookup_user and after that save_contact. In case of PA I didn't have lookup_user at all, just like you said:)
Cheers tomasz
It should work if neither registrar nor PA use UIDs or if both registrar and PA use UIDs. But if one of them uses UID and the other one not, it should NOT work...
Vaclav
On Mon, Jun 11, 2007 at 09:48:10AM +0200, tzieleniewski wrote:
Hi Vaclav,
Thank you for help everything works fine now. I missed the lookup_user function and didn't have and uid avp loaded before the handle_*() method.
Cheers tomasz
I meant using lookup_domain and lookup_user functions in the script. Vaclav
On Wed, Jun 06, 2007 at 09:37:29PM +0200, TZieleniewski wrote:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Vaclav where should I use those modules?<br> Could you be please more precise:)<br> you mean to load those modules or use them in some specific way in the context pf presence??<br> <br> Thank you<br> Cheers tomasz<br> <br> Vaclav Kubart pisze: <blockquote cite="mid:20070605155449.GK3832@vencore.sip-server.net" type="cite"> <pre wrap="">So, I tried it and it works for me...
Are you using domain (domain -> did) + uri_db (username + did -> uid) modules?
VaclavOn Tue, Jun 05, 2007 at 02:57:34PM +0200, Vaclav Kubart wrote: </pre>
<blockquote type="cite"> <pre wrap="">Yes Tomasz, you are right. The NOTIFY should contain tuple with 'open' status if use_callbacks is set and the presentity is registered. I will look on it...
VaclavOn Tue, Jun 05, 2007 at 10:24:29AM +0200, TZieleniewski wrote: </pre> <blockquote type="cite"> <pre wrap=""><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Vaclav,<br> <br> Thank you, so that was my misunderstanding of 'time_interval':)<br> But When my UAa subscribes to the presence of another UAb wich is already registered <br> the NOTIFY message contains tuple with the closed state indicated for UAb. <br> Only after the UAb sends PUBLISH message there is an updated NOTIFY sent to UAa with status 'open'.<br> Shouldn't it be like this that if 'auth' module parameter is "none" and the user is registered the NOFITY message for <br> for this user contains tuple with status open??<br> <br> Cheers<br> tomasz<br> <br> Vaclav Kubart pisze: <blockquote cite=<a class="moz-txt-link-rfc2396E" href="mailto:mid:20070605074149.GE3832@vencore.sip-server.net">"mid:20070605074149.GE3832@vencore.sip-server.net"</a> type="cite"> <pre wrap="">Hi Tomasz, the 'timer_interval' parameter specifies the interval after which PA checks changes in the list of presentites (changed presence state, changed/expired subscriptions, ...). If there is a change, NOTIFY corresponding with the change is sent, but if no change found, no NOTIFY is sent. Isn't this your problem?
VaclavOn Mon, Jun 04, 2007 at 05:02:12PM +0200, tzieleniewski wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi,
I am using SER rel_2_0_0. I am trying to set up a presence server as a simple PA.
I am using xlite UA and when UA registers and subscribes to a particular user presence Event SER doesn't sent a NOTIFY according to the 'time_interval' module parameter. It only responses with the 'immediate NOTIFY' with the closed status tuple. According to my configuration SER should sent a NOTIFY every 15 seconds and it doesn't do it at all. I kindly ask for your feedback.
Below I attached my module configuration and messages exchanged with UA. # -- pa params -- modparam("pa", "default_expires",300) modparam("pa", "max_subscription_expiration", 3600) modparam("pa", "max_publish_expiration", 3600) modparam("pa", "use_db", 1) modparam("pa", "use_callbacks", 1) modparam("pa", "watcherinfo_notify", 0) modparam("pa", "use_offline_winfo", 0) modparam("pa", "offline_winfo_expiration", 259200) modparam("pa", "auth", "none") modparam("pa", "winfo_auth", "implicit") modparam("pa", "pres_rules_file", "presence-rules.xml") modparam("pa", "ignore_408_on_notify", 0) modparam("pa", "timer_inte
-
tzieleniewski -
Vaclav Kubart