[OpenSIPS-Users] [15066] WARNING:rr:after_strict: no socket found to match RR [1][XXX.XXX.XXX.XXX:5060]

[Brian Southworth]

Hi Bogan,

 
Thanks for the reply, so are you saying the load balancer will send the call over to the B2B and then to asterisk ?

Again sorry for my lack of knowledge there is still a lot I don’t understand or know.

 
Regards,

 
Brian Southworth

Communications Developer

 
From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] 
Sent: 12 February 2018 14:23
To: Brian Southworth <brian.southworth at clocom.uk>; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] [15066] WARNING:rr:after_strict: no socket found to match RR [1][XXX.XXX.XXX.XXX:5060]

 
Hi Brian,

In this case, I guess that the OPenSIPS B2B (handling the REFER) should sit between the OpenSIPS LB and Asterisk - again , this is the case only if the result of the transfer is a call to an Asterisk box too. If the call may be redirected back to a carrier, the OpenSIPS B2B should sit in front of the LB.

Regards,



Bogdan-Andrei Iancu


 

OpenSIPS Founder and Developer


  http://www.opensips-solutions.com <http://www.opensips-solutions.com> 


OpenSIPS Summit 2018


  http://www.opensips.org/events/Summit-2018Amsterdam <http://www.opensips.org/events/Summit-2018Amsterdam> 

On 02/07/2018 03:38 PM, Brian Southworth wrote:

Opensips handles the refer sending it to the asterisk box

 
Regards,

 
Brian Southworth

Communications Developer




111 Wilmslow Road

Handforth

Wilmslow

SK9 3ER

 
T: 03333 446677

W: www.clocom.uk <http://www.clocom.uk/> 

		
 
	 

	 

 
 
From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org <mailto:bogdan at opensips.org> ] 
Sent: 07 February 2018 11:36
To: Brian Southworth <brian.southworth at clocom.uk> <mailto:brian.southworth at clocom.uk> ; OpenSIPS users mailling list <users at lists.opensips.org> <mailto:users at lists.opensips.org> 
Subject: Re: [OpenSIPS-Users] [15066] WARNING:rr:after_strict: no socket found to match RR [1][XXX.XXX.XXX.XXX:5060]

 
So the target of the refer is to another Asterisk or may be also back to the carrier ?





Bogdan-Andrei Iancu


 

OpenSIPS Founder and Developer


  http://www.opensips-solutions.com <http://www.opensips-solutions.com> 


OpenSIPS Summit 2018


  http://www.opensips.org/events/Summit-2018Amsterdam <http://www.opensips.org/events/Summit-2018Amsterdam> 

On 02/07/2018 01:32 PM, Brian Southworth wrote:

Hi Bogdan,

 
The Cisco phone, generates the refer once you press the xfer button when inside a call.

Caller àopensipsà asteriskàCarrier 

(cisco)

Regards,

 
Brian Southworth

 
T: 03333 446677

W: www.clocom.uk <http://www.clocom.uk/> 

				
				
			 

	 

 
From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org <mailto:bogdan at opensips.org> ] 
Sent: 07 February 2018 09:38
To: Brian Southworth <brian.southworth at clocom.uk> <mailto:brian.southworth at clocom.uk> ; OpenSIPS users mailling list <users at lists.opensips.org> <mailto:users at lists.opensips.org> 
Subject: Re: [OpenSIPS-Users] [15066] WARNING:rr:after_strict: no socket found to match RR [1][XXX.XXX.XXX.XXX:5060]

 
Hi Brian,

Which party is generating the REFER ? the asterisk boxes from behind the LB ? or the carrier side ?

and yes, see you in Amsterdam !!

Regards,





Bogdan-Andrei Iancu


 

OpenSIPS Founder and Developer


  http://www.opensips-solutions.com <http://www.opensips-solutions.com> 


OpenSIPS Summit 2018


  http://www.opensips.org/events/Summit-2018Amsterdam <http://www.opensips.org/events/Summit-2018Amsterdam> 

On 02/05/2018 05:52 PM, Brian Southworth wrote:

I think I get it now thank you Bogdan.

So I would forward the traffic using the opensips proxy, using the if (is_method(“refer”)) to the opensips box that would be the B2BUA? To bridge the call ?.

 
Also look forward to Opensips summit in may 😊 ill see you all there got it booked Saturday 😊

 
Regards,

 
Brian Southworth

 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20180212/d5364e71/attachment-0001.html>