Hi,
I'm having some problems when using topology hiding. In my scenario an
INVITE comes in to the opensips (SBC) instance from another opensips
instance (Proxy). It is routed to a callee which eventually answers with a
200OK. The 200 OK is routed through the SBC to the Proxy which answers back
wit
Hi, Royee!
Can you turn on debugging for this call and send the logs (in private if
privacy is an issue)?
My assumption is that the dialog is created before fix_nated_contact()
is called, perhaps due to a siptrace() call or something, and the wrong
contact ends up in the dialog. Or perhaps fix
Razvan,
Thanks for the help!
fix_nated_contact is called before create_dialog as you can also see from
the configuration file I added in the previous email.
When using the MI command I see:
callee_contact:: sip:USERNAME@PRIVATE_IP:PORT;transport=TCP
So it seems like the dialog is created with
Hi, Royee!
Can you make sure that fix_nated_contact() is called before create_dialog()?
Also, if you run through MI the dlg_list_ctx command, what is the
contact header stored in the dialog?
Best regards,
Răzvan
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 06/06/2017 11:02
Adding capture
On Mon, Jun 5, 2017 at 3:15 PM Royee Tichauer
wrote:
> Hi,
>
> I'm having some problems when using topology hiding. In my scenario an
> INVITE comes in to the opensips (SBC) instance from another opensips
> instance (Proxy). It is routed to a callee which eventually answers with a
Hi,
I'm having some problems when using topology hiding. In my scenario an
INVITE comes in to the opensips (SBC) instance from another opensips
instance (Proxy). It is routed to a callee which eventually answers with a
200OK. The 200 OK is routed through the SBC to the Proxy which answers back
wit
