THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Camille Oudot (coudot)
Attached to Project - sip-router
Summary - ims_registrar_scscf: unexpected 200 OK response after calling assign_server_unreg()
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - High
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Calling assign_server_unreg() leads to an unexpected 200 OK response, that seems to be sent by the registrar module itself (a Service-Route header is added):
SIP/2.0 200 OK
Via: (...)
Via: (...)
From: "+33XXXXXXXXX" <sip:+33XXXXXXXXX@(...)>;tag=as1202e009
To: <sip:+33YYYYYYYYY@(...)>;tag=d076ed28abef1b854449e88a91b18042-9f9b
Call-ID: 3e2203d25ce6ed30692ab44508d1eef7@(...):5060
CSeq: 102 INVITE
Service-Route: <sip:orig@scscf1.xxxxx.net;lr>
Server: SCSCF OIC G01R01C00
Content-Length: 0
No response should be sent by the ims_registrar_scscf module for this particular function. The response should probably be sent later by the script or an application server.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=309
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
Jason Penton has taken ownership of the following task:
FS#305 - Crash in ims_registrar_scscf caused by log
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=305
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
Jason Penton has taken ownership of the following task:
FS#308 - P-Served-User header on IMS ISC interface
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=308
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
Jason Penton has taken ownership of the following task:
FS#304 - Segfault in ims_auth's ims_proxy_authenticate function when IMPU != IMPI
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=304
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Camille Oudot (coudot)
Attached to Project - sip-router
Summary - P-Served-User header on IMS ISC interface
Task Type - Improvement
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Hi,
I have made a patch for the ims_isc module to add support for P-Served-User header on the ISC interface. This header allows a triggered Application Server to know the IMS user for who it was triggered, and in what state (originating/terminating, registered/unregistered).
Our application servers can't live without it. Moreover, this header have been normalized in RFC 5502, so it would be nice to support it in ims_isc.
This patch doesn't do anything complicated, only text formating, since all required informations were available in the module's internal data.
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=308
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Good evening.
Playing with latest "dialog module" versions (3.2, 3.3 and 4.0) I think
there could be an open "issue" with regard to dialog state management.
You can see on "dlg_handlers.c" on "dlg_onroute" function. On this last
when you receive a BYE message it fires some CallBacks.
I you receive a close second BYE, this last one destroys the dialog because
"dlg_release" function is called from a parallel process avoiding the other
processes callback execution.
I know a second BYE it's not a normal circumstance but you know, the real
world .
I think dialog_ng doesn't have this issue but also it has no DB support.
Thanks and regards.
--
Eduardo Lejarreta.