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:[email protected]] 
Sent: Monday, October 24, 2016 11:59 AM
To: OpenSIPS users mailling list <[email protected]>; johan de clercq
<[email protected]>
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
> [email protected]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

Attachment: opensips_problem.cfg
Description: Binary data

<?xml version="1.0"?>
<scenario id="refer" name="Handle refer at server" param="0" type="script">
  <init>
    <bridge>
      <server>
        <id>server1</id>
      </server>
      <client>
        <id>client1</id>
        <type>message</type>
        <destination>
          <value type="initial">server1</value>
        </destination>
      </client>
    </bridge>
  </init>

  <rules>
     <request>
       <refer>
	     <rule id="1">
		   <condition>
		     <state>2</state>
		   </condition>
           <action>
		     <state>1</state>
		     <send_reply>
               <code>202</code>
               <reason>Accepted</reason>
             </send_reply>
             <end_dialog_leg/>
             <bridge>
               <client>
                 <peer/>
               </client>
               <client>
                 <id>client2</id>
                 <destination>
                   <value type="header">Refer-To</value>
                 </destination>
               </client>
             </bridge>
           </action>
         </rule>
		 <rule id="2">
           <action>
            <state>2</state> 
		   </action>
         </rule>
       </refer>
    </request>
  </rules>
</scenario>

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

Reply via email to