[OpenSIPS-Users] Delivery Status Notification (Failure)
johan de clercq
johan at democon.be
Mon Oct 24 17:24:31 CEST 2016
What I can do is use multiple instances.
Instance 1 : do header changes and rewritehostport to instance 2
Instance 2 : do b2bua scenario and route to instance 3
Instance 3 : do the actual work.
From: johan de clercq [mailto:johan at democon.be]
Sent: Monday, October 24, 2016 1:56 PM
To: 'Bogdan-Andrei Iancu' <bogdan at opensips.org>; 'OpenSIPS users mailling
list' <users at lists.opensips.org>
Subject: RE: [OpenSIPS-Users] Delivery Status Notification (Failure)
The refer-to header looks like this:
"<sip:81005 at psx.democon.be;user=phone?Replaces=bf0cbd3f-33c16b5c-ac88f411%40
And I think that in order for the scenario to work, it should have the
following layout :
<sip:81005 at psx.democon.be>
So that's the manipulation that I want to do :
Extract part before ; and add >
From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
Sent: Monday, October 24, 2016 12:24 PM
To: johan de clercq <johan at democon.be>; 'OpenSIPS users mailling list'
<users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Delivery Status Notification (Failure)
The REFER request will never get into your script as it will be absorbed and
handled by the b2b module - actually will not see any sequential requests
for a call that was pushed into b2b.
What kind of manipulation you want to do over the REFER-TO hdr ?
OpenSIPS Founder and Developer
On 24.10.2016 13:06, johan de clercq wrote:
> Thanks Bogdan,
> The problem is that I have my refer-to header with replaces: in it.
> Hence I adapted the scenario so that I could do header manipulations
> on this header.
> I do however manipulations on headers and I think I need to reroute
> then through route(0)
> #x contains the value of the Refer-To header==$rt
> #remove the Refer-To header
> #manipulate x : extract part before ; and add >
> $var(x)=$var(x) + ">";
> #re route through route
> Hence I have 2 states in the scenario, so that on the first pass the
> scenario only puts state to 2 and then on the second pass, it should
> effectively bridge.
> There is of course a however :-): opensips does not start ...
> Oct 24 11:28:55  ERROR:core:fix_actions: called route 4 is not
> defined Oct 24 11:28:55  ERROR:core:fix_actions: fixing failed
> (code=-6) at cfg line 125 Oct 24 11:28:55  ERROR:core:main:
> failed to fix configuration with err code -6
> The problem is that I have nowhere a route 4 defined ..
> Can it be that route(0) is the problem ? If yes, how can I implement the
> above described logic ?
> BR, Johan.
> -----Original Message-----
> From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
> Sent: Monday, October 24, 2016 11:59 AM
> To: OpenSIPS users mailling list <users at lists.opensips.org>; johan de
> clercq <johan at democon.be>
> Subject: Re: [OpenSIPS-Users] Delivery Status Notification (Failure)
> Hi Johan,
> The cfg is more than simple and straight - whatever initial request
> you receive -> start the b2b with this scenario.
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> On 22.10.2016 17:45, johan de clercq wrote:
>> Does somebody has an example .cfg file that shows how to use the
>> refer scenario described in
>> http://www.opensips.org/Documentation/Tutorials-B2BUA#toc15 ?
>> I am struggling with call transfers with REFER and opensips that
> loadbalances to multiple gateways.
>> Johan De Clercq, Managing Director
>> Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke
>> Tel +3256980990 - GSM +32478720104
>> Users mailing list
>> Users at lists.opensips.org
More information about the Users