I'm testing the presence module on 0.10.99-dev in CVS.
When using the newest X-lite client I am getting the following error messages in /var/log/messages
/usr/local/sbin/ser[30891]: INFO: rls_mod.c:155: reading RLS data from database /usr/local/sbin/ser[30879]: INFO: subscribe.c:286: Unsupported event package /usr/local/sbin/ser[30879]: ERROR: subscribe.c:590: Error while checking message /usr/local/sbin/ser[30879]: INFO: subscribe.c:603: handle_subscription about to send_reply and return -2 /usr/local/sbin/ser[30885]: Warning: run_failure_handlers: no UAC support (0, 256) /usr/local/sbin/ser[30885]: WARN: rl_subscription.c:398: destroying subscription from callback due to 420 response on NOTIFY /usr/local/sbin/ser[30885]: TRACE: rl_subscription.c:400: RLS: subscription destroyed!!!
In X-lite I get this error message:
[07-01-30]15:44:45.526 | Debug | RESIP:TRANSACTION | "Match!" | [07-01-30]15:44:45.526 | Debug | RESIP:TRANSACTION | "Send to TU: TU: DialogUsageManager size=0 NOTIFY sip:tuser@192.168.1.35:34492 SIP/2.0 Via: SIP/2.0/UDP 85.112.135.70;branch=z9hG4bK7ed6.d015cec1.0 Max-Forwards: 70 Require: eventlist Contact: sip:85.112.135.70:5060 To: ""Jens""sip:tuser@test-domain.com;tag=d204727a From: sip:tuser@test-domain.com;tag=a6a1c5f60faecf035a1ae5b6e96e979a-1a1f Call-ID: OTYwMDE1NmQ5MDQwYjFmMTBlZjQ0NTNhZTExNWM4MGM. CSeq: 10 NOTIFY Content-Type: multipart/related;type=""application/rlmi+xml"";start=""qwW1099041416pPdxX1162343142"";boundary=""RewXdpxR741013657xA447338541""; User-Agent: Sip EXpress router(0.10.99-dev66 (i386/linux)) Subscription-State: active;expires=300 Event: presence Content-Length: 338
--RewXdpxR741013657xA447338541 Content-Transfer-Encoding: binary Content-ID: qwW1099041416pPdxX1162343142 Content-Type: application/rlmi+xml;charset=""UTF-8""
<?xml version=""1.0""?> <list xmlns=""urn:ietf:params:xml:ns:rlmi"" uri=""sip:tuser@test-domain.com"" version=""0"" fullState=""true""> </list>
--RewXdpxR741013657xA447338541--
" | [07-01-30]15:44:45.526 | Debug | RESIP | "SipMessage::getContents: multipart/related" | [07-01-30]15:44:45.526 | Debug | RESIP:DUM | "Decrypted message:02815028 " | [07-01-30]15:44:45.526 | Info | RESIP:DUM | "Got: SipReq: NOTIFY tuser@192.168.1.35:34492 tid=7ed6.d015cec1.0 cseq=NOTIFY contact=85.112.135.70:5060 / 10 from(wire)" | [07-01-30]15:44:45.526 | Info | RESIP:DUM | "Received an unsupported option tag(s): SipReq: NOTIFY tuser@192.168.1.35:34492 tid=7ed6.d015cec1.0 cseq=NOTIFY contact=85.112.135.70:5060 / 10 from(wire)" | [07-01-30]15:44:45.526 | Debug | RESIP | "Helper::makeResponse(SipReq: NOTIFY tuser@192.168.1.35:34492 tid=7ed6.d015cec1.0 cseq=NOTIFY contact=85.112.135.70:5060 / 10 from(wire) code=420 reason=" | [07-01-30]15:44:45.526 | Debug | RESIP | "SEND: SipResp: 420 tid=7ed6.d015cec1.0 cseq=NOTIFY / 10 from(tu)" | [07-01-30]15:44:45.527 | Debug | RESIP:DUM | "Failed required options validation NOTIFY sip:tuser@192.168.1.35:34492 SIP/2.0 Via: SIP/2.0/UDP 85.112.135.70;branch=z9hG4bK7ed6.d015cec1.0 Max-Forwards: 70 Require: eventlist Contact: sip:85.112.135.70:5060 To: ""Jens""sip:tuser@test-domain.com;tag=d204727a From: sip:tuser@test-domain.com;tag=a6a1c5f60faecf035a1ae5b6e96e979a-1a1f Call-ID: OTYwMDE1NmQ5MDQwYjFmMTBlZjQ0NTNhZTExNWM4MGM. CSeq: 10 NOTIFY Content-Type: multipart/related;type=""application/rlmi+xml"";boundary=""RewXdpxR741013657xA447338541"";start=""qwW1099041416pPdxX1162343142"" User-Agent: Sip EXpress router(0.10.99-dev66 (i386/linux)) Subscription-State: active;expires=300 Event: presence Content-Length: 334
--RewXdpxR741013657xA447338541 Content-Type: application/rlmi+xml;charset=""UTF-8"" Content-Transfer-Encoding: binary Content-Id: qwW1099041416pPdxX1162343142
<?xml version=""1.0""?> <list xmlns=""urn:ietf:params:xml:ns:rlmi"" uri=""sip:tuser@test-domain.com"" version=""0"" fullState=""true""> </list>
-
Does any know know how to solve this problem? Is there any other clients that works well with the ser presence module?
Kind regards, Jens-Martin Groenne
According to messages it seems to me, that your client is not able to handle "list NOTIFY". Such notifications are sent from RLS module, if a client subscribes to a resource-list URI not to a "simple URI".
This problem could cause that RLS was implemented according to an older draft version or because client simply doesn't support list notifications.
Is it working with non-list notifications? I.e. try to subscribe to an existing user (for example to sip:tuser@test-domain.com) and see if everything is ok.
Vaclav
On Tue, Jan 30, 2007 at 04:01:09PM +0100, Jens-Martin Groenne wrote:
I'm testing the presence module on 0.10.99-dev in CVS.
When using the newest X-lite client I am getting the following error messages in /var/log/messages
/usr/local/sbin/ser[30891]: INFO: rls_mod.c:155: reading RLS data from database /usr/local/sbin/ser[30879]: INFO: subscribe.c:286: Unsupported event package /usr/local/sbin/ser[30879]: ERROR: subscribe.c:590: Error while checking message /usr/local/sbin/ser[30879]: INFO: subscribe.c:603: handle_subscription about to send_reply and return -2 /usr/local/sbin/ser[30885]: Warning: run_failure_handlers: no UAC support (0, 256) /usr/local/sbin/ser[30885]: WARN: rl_subscription.c:398: destroying subscription from callback due to 420 response on NOTIFY /usr/local/sbin/ser[30885]: TRACE: rl_subscription.c:400: RLS: subscription destroyed!!!
In X-lite I get this error message:
[07-01-30]15:44:45.526 | Debug | RESIP:TRANSACTION | "Match!" | [07-01-30]15:44:45.526 | Debug | RESIP:TRANSACTION | "Send to TU: TU: DialogUsageManager size=0 NOTIFY sip:tuser@192.168.1.35:34492 SIP/2.0 Via: SIP/2.0/UDP 85.112.135.70;branch=z9hG4bK7ed6.d015cec1.0 Max-Forwards: 70 Require: eventlist Contact: sip:85.112.135.70:5060 To: ""Jens""sip:tuser@test-domain.com;tag=d204727a From: sip:tuser@test-domain.com;tag=a6a1c5f60faecf035a1ae5b6e96e979a-1a1f Call-ID: OTYwMDE1NmQ5MDQwYjFmMTBlZjQ0NTNhZTExNWM4MGM. CSeq: 10 NOTIFY Content-Type: multipart/related;type=""application/rlmi+xml"";start=""qwW1099041416pPdxX1162343142"";boundary=""RewXdpxR741013657xA447338541""; User-Agent: Sip EXpress router(0.10.99-dev66 (i386/linux)) Subscription-State: active;expires=300 Event: presence Content-Length: 338
--RewXdpxR741013657xA447338541 Content-Transfer-Encoding: binary Content-ID: qwW1099041416pPdxX1162343142 Content-Type: application/rlmi+xml;charset=""UTF-8""
<?xml version=""1.0""?>
<list xmlns=""urn:ietf:params:xml:ns:rlmi"" uri=""sip:tuser@test-domain.com"" version=""0"" fullState=""true"">
</list>
--RewXdpxR741013657xA447338541--
" | [07-01-30]15:44:45.526 | Debug | RESIP | "SipMessage::getContents: multipart/related" | [07-01-30]15:44:45.526 | Debug | RESIP:DUM | "Decrypted message:02815028 " | [07-01-30]15:44:45.526 | Info | RESIP:DUM | "Got: SipReq: NOTIFY tuser@192.168.1.35:34492 tid=7ed6.d015cec1.0 cseq=NOTIFY contact=85.112.135.70:5060 / 10 from(wire)" | [07-01-30]15:44:45.526 | Info | RESIP:DUM | "Received an unsupported option tag(s): SipReq: NOTIFY tuser@192.168.1.35:34492 tid=7ed6.d015cec1.0 cseq=NOTIFY contact=85.112.135.70:5060 / 10 from(wire)" | [07-01-30]15:44:45.526 | Debug | RESIP | "Helper::makeResponse(SipReq: NOTIFY tuser@192.168.1.35:34492 tid=7ed6.d015cec1.0 cseq=NOTIFY contact=85.112.135.70:5060 / 10 from(wire) code=420 reason=" | [07-01-30]15:44:45.526 | Debug | RESIP | "SEND: SipResp: 420 tid=7ed6.d015cec1.0 cseq=NOTIFY / 10 from(tu)" | [07-01-30]15:44:45.527 | Debug | RESIP:DUM | "Failed required options validation NOTIFY sip:tuser@192.168.1.35:34492 SIP/2.0 Via: SIP/2.0/UDP 85.112.135.70;branch=z9hG4bK7ed6.d015cec1.0 Max-Forwards: 70 Require: eventlist Contact: sip:85.112.135.70:5060 To: ""Jens""sip:tuser@test-domain.com;tag=d204727a From: sip:tuser@test-domain.com;tag=a6a1c5f60faecf035a1ae5b6e96e979a-1a1f Call-ID: OTYwMDE1NmQ5MDQwYjFmMTBlZjQ0NTNhZTExNWM4MGM. CSeq: 10 NOTIFY Content-Type: multipart/related;type=""application/rlmi+xml"";boundary=""RewXdpxR741013657xA447338541"";start=""qwW1099041416pPdxX1162343142"" User-Agent: Sip EXpress router(0.10.99-dev66 (i386/linux)) Subscription-State: active;expires=300 Event: presence Content-Length: 334
--RewXdpxR741013657xA447338541 Content-Type: application/rlmi+xml;charset=""UTF-8"" Content-Transfer-Encoding: binary Content-Id: qwW1099041416pPdxX1162343142
<?xml version=""1.0""?>
<list xmlns=""urn:ietf:params:xml:ns:rlmi"" uri=""sip:tuser@test-domain.com"" version=""0"" fullState=""true"">
</list>
Does any know know how to solve this problem? Is there any other clients that works well with the ser presence module?
Kind regards, Jens-Martin Groenne
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Vaclav Kubart wrote:
According to messages it seems to me, that your client is not able to handle "list NOTIFY". Such notifications are sent from RLS module, if a client subscribes to a resource-list URI not to a "simple URI".
This problem could cause that RLS was implemented according to an older draft version or because client simply doesn't support list notifications.
Is it working with non-list notifications? I.e. try to subscribe to an existing user (for example to sip:tuser@test-domain.com) and see if everything is ok.
Vaclav
Do you know any clients that handles list NOTIFY as they are in SER now?
When i try non-list notification I get the same error: In /var/log/messages /usr/local/sbin/ser[30885]: INFO: subscribe.c:603: handle_subscription about to send_reply and return -2 /usr/local/sbin/ser[30876]: Warning: run_failure_handlers: no UAC support (0, 256) /usr/local/sbin/ser[30876]: WARN: rl_subscription.c:398: destroying subscription from callback due to 420 response on NOTIFY
In X-lite debug log:
--RewXdpxR455586034xA1690507469--
" | [07-01-31]11:58:09.479 | Debug | RESIP | "SipMessage::getContents: multipart/related" | [07-01-31]11:58:09.479 | Debug | RESIP:DUM | "Decrypted message:0280D230 " | [07-01-31]11:58:09.480 | Info | RESIP:DUM | "Got: SipReq: NOTIFY tuser@192.168.1.71:54364 tid=d50c.16d08897.0 cseq=NOTIFY contact=192.168.1.1:5060 / 10 from(wire)" | [07-01-31]11:58:09.480 | Info | RESIP:DUM | "Received an unsupported option tag(s): SipReq: NOTIFY tuser@192.168.1.71:54364 tid=d50c.16d08897.0 cseq=NOTIFY contact=192.168.1.1:5060 / 10 from(wire)" | [07-01-31]11:58:09.480 | Debug | RESIP | "Helper::makeResponse(SipReq: NOTIFY tuser@192.168.1.71:54364 tid=d50c.16d08897.0 cseq=NOTIFY contact=192.168.1.1:5060 / 10 from(wire) code=420 reason=" | [07-01-31]11:58:09.480 | Debug | RESIP | "SEND: SipResp: 420 tid=d50c.16d08897.0 cseq=NOTIFY / 10 from(tu)" | [07-01-31]11:58:09.480 | Debug | RESIP:DUM | "Failed required options validation NOTIFY sip:tuser@192.168.1.71:54364 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.1;branch=z9hG4bKd50c.16d08897.0 Max-Forwards: 70 Require: eventlist Contact: sip:192.168.1.1:5060 To: ""Jens""sip:tuser@test-domain.com;tag=5d062f5d From: sip:tuser2@test-domain.com;tag=a6a1c5f60faecf035a1ae5b6e96e979a-db3a Call-ID: OTk2MjgzNjNiYTUzMzFiNDIxMjRlNzE2MDRhZTBhMzI. CSeq: 10 NOTIFY Content-Type: multipart/related;type=""application/rlmi+xml"";boundary=""RewXdpxR455586034xA1690507469"";start=""qwW388818348pPdxX2033088910"" User-Agent: Sip EXpress router(0.10.99-dev66 (i386/linux)) Subscription-State: active;expires=300 Event: presence Content-Length: 336
--RewXdpxR455586034xA1690507469 Content-Type: application/rlmi+xml;charset=""UTF-8"" Content-Transfer-Encoding: binary Content-Id: qwW388818348pPdxX2033088910
<?xml version=""1.0""?> <list xmlns=""urn:ietf:params:xml:ns:rlmi"" uri=""sip:tuser2@test-domain.com"" version=""0"" fullState=""true""> </list>
--RewXdpxR455586034xA1690507469--" | [07-01-31]11:58:09.581 | Debug | RESIP:TRANSACTION | "Adding timer: Timer J tid=d50c.16d08897.0 ms=32000" | [07-01-31]11:58:09.581 | Debug | RESIP:TRANSPORT | "Looked up source for destination: [ V4 192.168.1.1:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:54364 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] -> [ V4 192.168.1.71:0 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:54364 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] sent-by=192.168.1.1 sent-port=0" | [07-01-31]11:58:09.581 | Debug | RESIP:TRANSPORT | "Transmitting to [ V4 192.168.1.1:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:54364 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] tlsDomain= via [ V4 192.168.1.71:54364 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:54364 UDP target domain=unspecified connectionId=0 ] connectionId=0 ]SIP/2.0 420 Bad Extension Via: SIP/2.0/UDP 192.168.1.1;branch=z9hG4bKd50c.16d08897.0 To: ""Jens""sip:tuser@test-domain.com;tag=5d062f5d From: sip:tuser2@test-domain.com;tag=a6a1c5f60faecf035a1ae5b6e96e979a-db3a Call-ID: OTk2MjgzNjNiYTUzMzFiNDIxMjRlNzE2MDRhZTBhMzI. CSeq: 10 NOTIFY Unsupported: eventlist Content-Length: 0
Kind regards, Jens-Martin Groenne
It is still list notification. Could you send me dump of SUBSCRIBE request which was sent from XLite? Vaclav
Do you know any clients that handles list NOTIFY as they are in SER now?
When i try non-list notification I get the same error: In /var/log/messages /usr/local/sbin/ser[30885]: INFO: subscribe.c:603: handle_subscription about to send_reply and return -2 /usr/local/sbin/ser[30876]: Warning: run_failure_handlers: no UAC support (0, 256) /usr/local/sbin/ser[30876]: WARN: rl_subscription.c:398: destroying subscription from callback due to 420 response on NOTIFY
In X-lite debug log:
--RewXdpxR455586034xA1690507469--
" | [07-01-31]11:58:09.479 | Debug | RESIP | "SipMessage::getContents: multipart/related" | [07-01-31]11:58:09.479 | Debug | RESIP:DUM | "Decrypted message:0280D230 " | [07-01-31]11:58:09.480 | Info | RESIP:DUM | "Got: SipReq: NOTIFY tuser@192.168.1.71:54364 tid=d50c.16d08897.0 cseq=NOTIFY contact=192.168.1.1:5060 / 10 from(wire)" | [07-01-31]11:58:09.480 | Info | RESIP:DUM | "Received an unsupported option tag(s): SipReq: NOTIFY tuser@192.168.1.71:54364 tid=d50c.16d08897.0 cseq=NOTIFY contact=192.168.1.1:5060 / 10 from(wire)" | [07-01-31]11:58:09.480 | Debug | RESIP | "Helper::makeResponse(SipReq: NOTIFY tuser@192.168.1.71:54364 tid=d50c.16d08897.0 cseq=NOTIFY contact=192.168.1.1:5060 / 10 from(wire) code=420 reason=" | [07-01-31]11:58:09.480 | Debug | RESIP | "SEND: SipResp: 420 tid=d50c.16d08897.0 cseq=NOTIFY / 10 from(tu)" | [07-01-31]11:58:09.480 | Debug | RESIP:DUM | "Failed required options validation NOTIFY sip:tuser@192.168.1.71:54364 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.1;branch=z9hG4bKd50c.16d08897.0 Max-Forwards: 70 Require: eventlist Contact: sip:192.168.1.1:5060 To: ""Jens""sip:tuser@test-domain.com;tag=5d062f5d From: sip:tuser2@test-domain.com;tag=a6a1c5f60faecf035a1ae5b6e96e979a-db3a Call-ID: OTk2MjgzNjNiYTUzMzFiNDIxMjRlNzE2MDRhZTBhMzI. CSeq: 10 NOTIFY Content-Type: multipart/related;type=""application/rlmi+xml"";boundary=""RewXdpxR455586034xA1690507469"";start=""qwW388818348pPdxX2033088910"" User-Agent: Sip EXpress router(0.10.99-dev66 (i386/linux)) Subscription-State: active;expires=300 Event: presence Content-Length: 336
--RewXdpxR455586034xA1690507469 Content-Type: application/rlmi+xml;charset=""UTF-8"" Content-Transfer-Encoding: binary Content-Id: qwW388818348pPdxX2033088910
<?xml version=""1.0""?>
<list xmlns=""urn:ietf:params:xml:ns:rlmi"" uri=""sip:tuser2@test-domain.com"" version=""0"" fullState=""true"">
</list>
--RewXdpxR455586034xA1690507469--" | [07-01-31]11:58:09.581 | Debug | RESIP:TRANSACTION | "Adding timer: Timer J tid=d50c.16d08897.0 ms=32000" | [07-01-31]11:58:09.581 | Debug | RESIP:TRANSPORT | "Looked up source for destination: [ V4 192.168.1.1:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:54364 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] -> [ V4 192.168.1.71:0 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:54364 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] sent-by=192.168.1.1 sent-port=0" | [07-01-31]11:58:09.581 | Debug | RESIP:TRANSPORT | "Transmitting to [ V4 192.168.1.1:5060 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:54364 UDP target domain=unspecified connectionId=0 ] connectionId=0 ] tlsDomain= via [ V4 192.168.1.71:54364 UDP target domain=unspecified received on: Transport: [ V4 0.0.0.0:54364 UDP target domain=unspecified connectionId=0 ] connectionId=0 ]SIP/2.0 420 Bad Extension Via: SIP/2.0/UDP 192.168.1.1;branch=z9hG4bKd50c.16d08897.0 To: ""Jens""sip:tuser@test-domain.com;tag=5d062f5d From: sip:tuser2@test-domain.com;tag=a6a1c5f60faecf035a1ae5b6e96e979a-db3a Call-ID: OTk2MjgzNjNiYTUzMzFiNDIxMjRlNzE2MDRhZTBhMzI. CSeq: 10 NOTIFY Unsupported: eventlist Content-Length: 0
Kind regards, Jens-Martin Groenne
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Jens-Martin Groenne wrote:
I'm testing the presence module on 0.10.99-dev in CVS.
When using the newest X-lite client I am getting the following error messages in /var/log/messages
It seems X-lite (xten) has some problem with their presence implementation. When I use Gaim presence works somewhat better, but not perfect, I get online / offline status from the presence server, but it does not handle changes in status on users in the buddy list.
If anyone knows of other good presence / SIMPLE clients please let me know!
Kind regards, Jens-Martin Groenne
I used EyeBeam and an older XLite - presence was working there... Basic presence (non-list) was working with large number of clients (kphone, EyeBeam, Windows Messenger, XLite, pua.pl, ...) Vaclav
On Wed, Jan 31, 2007 at 01:36:37PM +0100, Jens-Martin Groenne wrote:
Jens-Martin Groenne wrote:
I'm testing the presence module on 0.10.99-dev in CVS.
When using the newest X-lite client I am getting the following error messages in /var/log/messages
It seems X-lite (xten) has some problem with their presence implementation. When I use Gaim presence works somewhat better, but not perfect, I get online / offline status from the presence server, but it does not handle changes in status on users in the buddy list.
If anyone knows of other good presence / SIMPLE clients please let me know!
Kind regards, Jens-Martin Groenne
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Jens-Martin Groenne -
Vaclav Kubart