-
Hi. Please use the maillist for such a question as it's not a bug report.
First of all, sending two NOTIFY's when logging out is a bad idea as it makes no sense (the first one sets "invisible" status and the second one expires the presentity).
Please ask this question in the mailist and we'll keep discussing about it ;)
2009-10-12 10:29:20 UTC in OpenSIPS/OpenSER-a versatile SIP Server
-
The error is 100% reproducible.
2009-08-25 14:58:00 UTC in OpenSIPS/OpenSER-a versatile SIP Server
-
Sorry, the scenario is the following (two crashes confirmed):
- alice allows bob in pres-rules.
- bob subscribes to alice and receives NOTIFY "active".
- "active_watches" and "watchers" contain an entry with status = 1.
- alice removes bob from pres-rules document.
- OpenSIPS sends NOTIFY "terminated;deactivated".
- bob subscribes again and OpenSIPS replies NOTIFY "pending".
-...
2009-08-25 14:38:40 UTC in OpenSIPS/OpenSER-a versatile SIP Server
-
Scenario:
- alice allows bob in pres-rules.
- bob subscribes to alice and receives NOTIFY "active".
- "active_watches" and "watchers" contain an entry with status = 1.
- alice removes bob from pres-rules document.
- OpenSIPS crashes.
gdb backtrace:
-----------------------------------
#0 0x00007fe8b40a1ac9 in db_mysql_val2bind (v=0x7fffbce46cd0, binds=0x754630, i=
2009-08-25 14:30:09 UTC in OpenSIPS/OpenSER-a versatile SIP Server
-
I've added a xlog to display the $retcode after rls_handle_subscribe():
*** rls_handle_subscribe() for sip:eyebeam2@example.net => rc = 5 ***
*** rls_handle_subscribe() for sip:alice@example.net => rc = 18446744073709551615 ***
*** rls_handle_subscribe() for sip:eyebeam@example.net;transport=tcp => rc = 5 ***
*** rls_handle_subscribe() for sip:xlite@example.net => rc =...
2009-08-11 16:43:56 UTC in OpenSIPS/OpenSER-a versatile SIP Server
-
Typical conf:
--------------------
modparam("rls", "to_presence_code", 5)
[...]
rls_handle_subscribe();
if ($retcode==5) {
#RLS indicated that message should be processed by presence.
handle_subscribe();
}
exit;
--------------------
If the SUBSCRIBE arrives with a parameter in the RURI (i.e; sip:alice@example.org;transport=tcp) then "rls_handle_subscribe()" doesnt' return 5...
2009-08-11 14:59:33 UTC in OpenSIPS/OpenSER-a versatile SIP Server
-
Please, ask such a question in the users maillist as most probably it's a bug in your configuration.
Use the tracker to report bugs, and not to ask questions.
Thanks.
2009-08-09 17:51:26 UTC in OpenSIPS/OpenSER-a versatile SIP Server
-
Hi, I paste the HTTP trace from the report in the devel list:
---------------------------------------
GET /mobicents/org.openmobilealliance.pres-rules/users/sip:andaleeb1@192.168.0.133/pres-rules
HTTP/1.1
Host: 192.168.0.130:8080
Accept: */*
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.2.3.GA (build:
SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0
ETag...
2009-08-06 07:45:07 UTC in OpenSIPS/OpenSER-a versatile SIP Server
-
Vladimir, you are "solving" a problem which is not a problem. This just solves a *client* problem in your escenario but breaks RFC 3261 specifications since multiple AoR registrations are allowed from the same address:port.
I use Tinkle softphone which allows me having 10-50 different SIP accounts registered at the same time, and it uses the same address:port for all. This is perfectly valid...
2009-08-05 11:02:24 UTC in OpenSIPS/OpenSER-a versatile SIP Server
-
Hi Anca, just curiosity: any new on this issue? :)
2009-07-25 13:19:12 UTC in OpenSIPS/OpenSER-a versatile SIP Server
