Hi Robert,
OpenSBC can do hairpin if you do it correctly. The outbound call should
be sent through the main trunk
UA1 -> OSBC-Main-Trunk -> SIP-Server
When the SIP-Server hairpins/trombones the call back to OpenSBC, it must
either use one of two listeners based on which config applies
** SIP-Server has static routing policies
SIP-Server -> OSBC-BackDoor -> OSBC-Main-Trunk -> UA2
Or
** SIP-Server configured as a trunk provider
SIP-Server -> OSBC-SIP-Trunk -> OSBC-Main-Trunk -> UA2
In the case of the original poster, he is trying to trombone the call
back to the SIP-Trunk which would cause call-id collisions
Joegen
voice wrote:
> Hi
>
> I am using a inGate SBC and i am able to hairpin. I did run into a proble
> at first but it turned out to be something else. But along the way i was
> able to route inbound to the sipX by changing the port away form 5060,
> just pick one like 6070 then set up a rule that looked for and took traffic
> from port 6070 and set it Forward back to 5060 out to the SBC => ITSP. The
> other and final solution was changing the remote phone from Grandstream to
> Snom
> because Grandstream fails in all phones to manage RE-Invites. Lost two
> weeks screwing with the Grandstreams.
>
> AT&T analog phone <==> Sip trunk ITSP <==> ((inGate <==> sipX(
> registration ) back out <==> SiP Trunk ITSP)(high speed T1)) <==> and ring
> a ip phone connected to an AT&T DSL router in another part of the office.
>
> Don't do STUN. Do Outbound Proxy instead.
>
> r
>
>
|
