[Spce-user] SPCE internal routing

[John Murray]

Jon hi,

Thanks for that. Yes that is what I am using and it works in all scenarios
except the one described above.
I think this is due to the fact that the REFER does not pass through the
proxy.

Any ideas?

Thanks.

John
On 20 Sep 2013 12:35, "Jon Bonilla" <jbonilla at sipwise.com> wrote:

> El Fri, 20 Sep 2013 12:12:27 +0100
> "John Murray" <john.murray at skyracktelecom.com> escribió:
>
> > 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.
> >
>
> Hi john
>
> Not sure if it would work in all your scenarios but check in version 3.0 a
> option called "allow_refer_method". It should allow in-dialog REFER
> requests to
> be sent from one leg to another and whitelist the required headers in the
> sbc
> profile.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130920/a7a7bff9/attachment-0001.html>