[OpenSER-Devel] [ openser-Bugs-1948949 ] BYE2BYE Patch #1642890 not fully implemented in V1.3

SourceForge.net noreply at sourceforge.net
Sat May 10 23:49:08 CEST 2008


Bugs item #1948949, was opened at 2008-04-22 18:50
Message generated for change (Comment added) made by bogdan_iancu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1948949&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver 1.3.x
Status: Open
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Jim Burke (jimbohamez)
>Assigned to: Bogdan-Andrei Iancu (bogdan_iancu)
Summary: BYE2BYE Patch #1642890 not fully implemented in V1.3

Initial Comment:
After installing Openser Version 1.3 I found that the BYE2BYE patch submitted by EKobi was only partially implemented in the DIALOG module.

The dialog module has been changed and a way to send 'BYE' messages to both caller and callee via the MI_FIFO module were added, however no code was added in the procedure to handle timeouts.  Refer to openser/modules/dialog/dlg_handlers.c procedure dlg_ontimeout.

The BYE2BYE patch also added the following parameters that allow the script to process the BYE messages for billing purposes.

modparam("bye2bye","bye2bye_to_next_hop","sip:mydomain.com:5060")
modparam("bye2bye","bye2bye_from_next_hop","sip:mydomain.com:5060")

Regards,
Jim

----------------------------------------------------------------------

>Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2008-05-11 00:49

Message:
Logged In: YES 
user_id=1275325
Originator: NO

Hi Jim,

That part of the patch was not included as it breaks the RFC3261 - a
request within the dialog must be routed according the the routing set (RR
+ contact) and all proxies on the patch must respect this - so, if openser
generates a request within the dialog, it must follow this rule too and not
force different destinations for the messages.

A different solution to achieving the same functionality will be on the
way for 1.4

Regards,
Bogdan

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1948949&group_id=139143



More information about the Devel mailing list