[Spce-user] SPCE internal routing

[John Murray]

Jon hi,

We wanted to add call transfer function to our users so instead of adding an asterisk box to handle REFERs we got a module for SEMS to do this.
It works well but in a call where a local user is on the b-leg call and does an un-attended transfer, so sends a REFER message, this is received on the lb and loose routed to SEMS on port 5080 so the Refer-To: header, who is the new callee is not processed by the proxy.

Would it be best to have an exception on the lb to catch this and send to the proxy for processing?

Thanks very much.

John

-----Original Message-----
From: spce-user-bounces at lists.sipwise.com [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Jon Bonilla (Manwe)
Sent: 18 September 2013 10:12
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] SPCE internal routing

El Thu, 12 Sep 2013 23:36:23 +0100
"John Murray" <john.murray at skyracktelecom.com> escribió:

> Hello,
> 
>  
> 
> I see from the SPCE architecture that new INVITES come in through the 
> load balancer to the proxy for processing/gw lookup/etc. Then on to 
> sems as the B2BUA which ten sends straight to the lb for outbound delivery.
> 
>  
> 
> Is there a reason other than performance not to send the messages on 
> the b-leg from sems to the proxy and then to the lb?
> 
>  
> 
> I want to catch and process messages from the b-leg before they hit sems.
> 


Hi John. Callee preferences are already processes during the call. Why would you like to send the call back to the proxy?

In any case this would be a very difficult change to do.