Re: [OpenSIPStack] INVITE and multi via:

[<sa...@ER...>]

Hi eric

Yes, UA->OSBC->SIPX->OSBC->ITSP.  In our case we are using sip truck as
gateway.

ITSP have different Invite requirement mainly attributed to their security
concerns.  Good luck with your guide

Warren Kreckler

----- Original Message ----- 
From: "eric hernaez" <er...@so...>
To: <ope...@li...>
Sent: Tuesday, December 04, 2007 10:55 PM
Subject: Re: [OpenSIPStack] INVITE and multi via:


>
>
> jo...@op... wrote:
> > Hi Warren,
> >
> > If the call flow is Caller->sipX->SBC->ITSP, then OpenSBC would have
> > just sent a single via.  Is your call flow Caller->SBC->sipX->ITSP?
> >
> >
>
> We are working on publishing a How To guide for using OSBC with SIPX.
> But until that is ready, think about using SIPX as a gateway for all
> PSTN-bound calls so that the call flow would be as follows:
> UA->OSBC->SIPX->OSBC->ITSP.
>
> Since OSBC will be proxying the media for NAT traversal in most cases,
> having OSBC as a single IP address (for both signaling and media) known
> to your ITSP will simplify their configuration as well.
>
>
> > Joegen
> >
> > sales@ER wrote:
> >
> >> Hi
> >>
> >> Our ITSP can accept only 1 Via statement in an INVITE.  The INVITE when
it
> >> reaches the SBC has an entry from the phone and two from sipx. I cannot
find
> >> any documentation about an option to remove Via Headers.
> >>
> >> Warren Kreckler
> >>
> >>
> >
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell.  From the desktop to the data center, Linux is going
> mainstream.  Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel