[OpenSER-Devel] [ openser-Bugs-1739565 ] UAC - Module: uac_replace_from in Branch-Route

SourceForge.net noreply at sourceforge.net
Fri Jul 6 17:14:50 CEST 2007


Bugs item #1739565, was opened at 2007-06-19 08:53
Message generated for change (Comment added) made by carstenbock
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1739565&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.2.x
Status: Open
Resolution: Postponed
Priority: 5
Private: No
Submitted By: Carsten Bock (carstenbock)
Assigned to: Bogdan (bogdan_iancu)
Summary: UAC - Module: uac_replace_from in Branch-Route

Initial Comment:
Happy Birthday OpenSER!

Congrutulations here from Hamburg, Germany to all OpenSER  Core Developers and thank you to all contributors to the OpenSER Project: Let's keep up the great work!

I fixed a minor Bug in OpenSER 1.2 (and earlier): uac_replace_from (Module UAC) was not proper usable in Branch-Routes (the module prohibited the use in branches and it did not work properly).
In Auto-Mode, for each branch a From-Line would be added to the Reply, resulting in multiple From-Lines in the reply. Not really a problem, just not nice.
The reason for this was, that the TM-Callback was set twice: Once when calling uac_replace_from, and the second time, when the RR-Callback was executed. When looking at the source, i did also see, that the RR-Param was also added in "manual"-Mode, which seems not to be neccessary.

The attached patch fixes the following:
- No RR-Param in manual-mode
- only single "From"-Line in replies in auto-mode
- uac_replace_from now usable in branch_routes

The patch is against OpenSER 1.2.1. I will do further testing on this patch.

Carsten

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

>Comment By: Carsten Bock (carstenbock)
Date: 2007-07-06 15:14

Message:
Logged In: YES 
user_id=1488991
Originator: YES

Hi Bogdan,

I see your point, you're right. Possibly i'll have to think about this
issue a little more.

i need this functionality for different Call-Forward scenarios. Examples:
1) A customer of ours requires the From-Line to be the original
destination in the Forwarded Request; e.g.: A call B (From=A),
Call-Forward-Busy to C (From=B). This is the way, as it would be normal
here in Germany on the ISDN line :-(
2) For OnNet Destinations, we modify the From line to something
user-friendly (e.g. to "011-494012345" <sip:011494012345 at ...>). In case of
a call-forwarding, this From-Line has to be in Format recommended by the
ITU e.164...
3) In case of anonymous calls, we need different From-Lines depending on
the destination: Towards the CPE we need to send "Anonymous"
<sip:anonymous at hostname.invalid>; towards the PSTN (e.g. CF-Busy), we need
to send "Anonymous" <sip:494012345 at sip-server-ip>. This is a requirement by
our Gateway provider :-/

Carsten

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

Comment By: Bogdan (bogdan_iancu)
Date: 2007-07-06 11:12

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

Hi Carsten,

There are seversal issues with the patch:

1) in Manual mode you still need the RR-Param. If you read in the
documentation the meaning of the manual mode, you will see that it means
that all changes related to transaction are done automatically, but the
changes acros the dialog need to be done manually (and you need the
RR-param in order to restore - manual or auto - the original from in the
sequential requests)

2) if you do not not register the TM TMCB_RESPONSE_IN callback in auto
mode, the replies will not have the FROM hdr restored..

Maybe you can send me a scenario example in order to understand what you
want to do.

The support for from mangling in branch route is on purpose disabled as
there are know thinks not to work (like multiple callbacka, multipled hdrs,
etc)..

Regards,
Bogdan

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

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



More information about the Devel mailing list