Re: Delivery Status Notification (Failure)

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Delivery Status Notification (Failure)

Johan De Clercq

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
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Delivery Status Notification (Failure)

Bogdan-Andrei Iancu-2
Hi Johan,

The cfg is more than simple and straight - whatever initial request you
receive -> start the b2b with this scenario.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

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
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Delivery Status Notification (Failure)

Johan De Clercq
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)

  if(is_method("REFER"))
  {
        #x contains the value of the Refer-To header==$rt
        $var(x)=$rt;
        #remove the Refer-To header
        remove_hf("Refer-To");
        #manipulate x : extract part before ; and add >
        $var(x)=$(var(x){s.select,0,;});
        $var(x)=$var(x) + ">";
        append_hf("Refer-To:$var(x)");
        #re route through route[0]
        route(0);      
  }

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 [29804] ERROR:core:fix_actions: called route 4 is not
defined
Oct 24 11:28:55 [29804] ERROR:core:fix_actions: fixing failed (code=-6) at
cfg line 125
Oct 24 11:28:55 [29804] 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:[hidden email]]
Sent: Monday, October 24, 2016 11:59 AM
To: OpenSIPS users mailling list <[hidden email]>; johan de clercq
<[hidden email]>
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.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

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
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

opensips_problem.cfg (3K) Download Attachment
scenario_refer.xml (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Delivery Status Notification (Failure)

Bogdan-Andrei Iancu-2
Johan,

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 ?

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

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)
>
>    if(is_method("REFER"))
>    {
>          #x contains the value of the Refer-To header==$rt
>          $var(x)=$rt;
>          #remove the Refer-To header
>          remove_hf("Refer-To");
>          #manipulate x : extract part before ; and add >
>          $var(x)=$(var(x){s.select,0,;});
>          $var(x)=$var(x) + ">";
>          append_hf("Refer-To:$var(x)");
>          #re route through route[0]
>          route(0);
>    }
>
> 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 [29804] ERROR:core:fix_actions: called route 4 is not
> defined
> Oct 24 11:28:55 [29804] ERROR:core:fix_actions: fixing failed (code=-6) at
> cfg line 125
> Oct 24 11:28:55 [29804] 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:[hidden email]]
> Sent: Monday, October 24, 2016 11:59 AM
> To: OpenSIPS users mailling list <[hidden email]>; johan de clercq
> <[hidden email]>
> 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.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> 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
>> [hidden email]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Delivery Status Notification (Failure)

Johan De Clercq
The refer-to header looks like this:

"<sip:[hidden email];user=phone?Replaces=bf0cbd3f-33c16b5c-ac88f411%40
213.125.208.178%3Bto-tag%3DHjDD97H3getUQ%3Bfrom-tag%3DE23BB509-F55C93D6>"

And I think that in order for the scenario to work, it should have the
following layout :

<sip:[hidden email]>

So that's the manipulation that I want to do :

Extract part before ; and add >

BR,



-----Original Message-----
From: Bogdan-Andrei Iancu [mailto:[hidden email]]
Sent: Monday, October 24, 2016 12:24 PM
To: johan de clercq <[hidden email]>; 'OpenSIPS users mailling list'
<[hidden email]>
Subject: Re: [OpenSIPS-Users] Delivery Status Notification (Failure)

Johan,

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 ?

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

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)
>
>    if(is_method("REFER"))
>    {
>          #x contains the value of the Refer-To header==$rt
>          $var(x)=$rt;
>          #remove the Refer-To header
>          remove_hf("Refer-To");
>          #manipulate x : extract part before ; and add >
>          $var(x)=$(var(x){s.select,0,;});
>          $var(x)=$var(x) + ">";
>          append_hf("Refer-To:$var(x)");
>          #re route through route[0]
>          route(0);
>    }
>
> 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 [29804] ERROR:core:fix_actions: called route 4 is not
> defined Oct 24 11:28:55 [29804] ERROR:core:fix_actions: fixing failed
> (code=-6) at cfg line 125 Oct 24 11:28:55 [29804] 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:[hidden email]]
> Sent: Monday, October 24, 2016 11:59 AM
> To: OpenSIPS users mailling list <[hidden email]>; johan de
> clercq <[hidden email]>
> 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.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> 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
>> [hidden email]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>



_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Delivery Status Notification (Failure)

Johan De Clercq
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.

KR,

-----Original Message-----
From: johan de clercq [mailto:[hidden email]]
Sent: Monday, October 24, 2016 1:56 PM
To: 'Bogdan-Andrei Iancu' <[hidden email]>; 'OpenSIPS users mailling
list' <[hidden email]>
Subject: RE: [OpenSIPS-Users] Delivery Status Notification (Failure)

The refer-to header looks like this:

"<sip:[hidden email];user=phone?Replaces=bf0cbd3f-33c16b5c-ac88f411%40
213.125.208.178%3Bto-tag%3DHjDD97H3getUQ%3Bfrom-tag%3DE23BB509-F55C93D6>"

And I think that in order for the scenario to work, it should have the
following layout :

<sip:[hidden email]>

So that's the manipulation that I want to do :

Extract part before ; and add >

BR,



-----Original Message-----
From: Bogdan-Andrei Iancu [mailto:[hidden email]]
Sent: Monday, October 24, 2016 12:24 PM
To: johan de clercq <[hidden email]>; 'OpenSIPS users mailling list'
<[hidden email]>
Subject: Re: [OpenSIPS-Users] Delivery Status Notification (Failure)

Johan,

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 ?

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

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)
>
>    if(is_method("REFER"))
>    {
>          #x contains the value of the Refer-To header==$rt
>          $var(x)=$rt;
>          #remove the Refer-To header
>          remove_hf("Refer-To");
>          #manipulate x : extract part before ; and add >
>          $var(x)=$(var(x){s.select,0,;});
>          $var(x)=$var(x) + ">";
>          append_hf("Refer-To:$var(x)");
>          #re route through route[0]
>          route(0);
>    }
>
> 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 [29804] ERROR:core:fix_actions: called route 4 is not
> defined Oct 24 11:28:55 [29804] ERROR:core:fix_actions: fixing failed
> (code=-6) at cfg line 125 Oct 24 11:28:55 [29804] 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:[hidden email]]
> Sent: Monday, October 24, 2016 11:59 AM
> To: OpenSIPS users mailling list <[hidden email]>; johan de
> clercq <[hidden email]>
> 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.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> 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
>> [hidden email]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>




_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Delivery Status Notification (Failure)

Bogdan-Andrei Iancu-2
In reply to this post by Johan De Clercq
Johan,

The scenario should work with the received value too . Whatever is
between the <> is considered as SIP URI and it will copied into the RURI
of the new call.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 24.10.2016 14:55, johan de clercq wrote:

> The refer-to header looks like this:
>
> "<sip:[hidden email];user=phone?Replaces=bf0cbd3f-33c16b5c-ac88f411%40
> 213.125.208.178%3Bto-tag%3DHjDD97H3getUQ%3Bfrom-tag%3DE23BB509-F55C93D6>"
>
> And I think that in order for the scenario to work, it should have the
> following layout :
>
> <sip:[hidden email]>
>
> So that's the manipulation that I want to do :
>
> Extract part before ; and add >
>
> BR,
>
>
>
> -----Original Message-----
> From: Bogdan-Andrei Iancu [mailto:[hidden email]]
> Sent: Monday, October 24, 2016 12:24 PM
> To: johan de clercq <[hidden email]>; 'OpenSIPS users mailling list'
> <[hidden email]>
> Subject: Re: [OpenSIPS-Users] Delivery Status Notification (Failure)
>
> Johan,
>
> 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 ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> 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)
>>
>>     if(is_method("REFER"))
>>     {
>>           #x contains the value of the Refer-To header==$rt
>>           $var(x)=$rt;
>>           #remove the Refer-To header
>>           remove_hf("Refer-To");
>>           #manipulate x : extract part before ; and add >
>>           $var(x)=$(var(x){s.select,0,;});
>>           $var(x)=$var(x) + ">";
>>           append_hf("Refer-To:$var(x)");
>>           #re route through route[0]
>>           route(0);
>>     }
>>
>> 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 [29804] ERROR:core:fix_actions: called route 4 is not
>> defined Oct 24 11:28:55 [29804] ERROR:core:fix_actions: fixing failed
>> (code=-6) at cfg line 125 Oct 24 11:28:55 [29804] 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:[hidden email]]
>> Sent: Monday, October 24, 2016 11:59 AM
>> To: OpenSIPS users mailling list <[hidden email]>; johan de
>> clercq <[hidden email]>
>> 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.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developer
>> http://www.opensips-solutions.com
>>
>> 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
>>> [hidden email]
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users