Closed wackazong closed 9 years ago
OverSIP does not rewrite the To header (unless you do that in the server.rb script). A SIP trace of the incoming SIP request and the outgoing SIP request would be very useful.
However, please use the OverSIP public mailing list for these kind of question/issues.
Ok, thanks.
It appears to me that OverSIP is handling this INVITE incorrectly. Can you please comment?
Architecture: sipML5 client -> OverSIP -> OpenSips Edge Proxy -> OpenSips Serving Server. Both clients are sipML5. OverSIP and the OpenSIPS edge proxy are on the same machine on Amayzon EC2.
From client (sipML5):
OverSIP log:
It appears to me that OverSIP changes the TO: header from
sip:sq4ZYs1y5Ijlg3dkABeBR@staging.sipheadstore.com
tosips:sq4ZYs1y5Ijlg3dkABeBR@df7jal23ls0d.invalid;rtcweb-breaker=no;transport=wss;ov-ob=2e60ea402d
The INVITE is then forwarded to the EDGE server of our SIP network running OpenSIPS, and there we get problems:
Thanks for any advice.
The underlying problem is that the BYE at the end of the call does not get forwarded to the callee if the caller ends the connection. It seems to me that the initial culprit is the df7jal23ls0d.invalid domain in the to: header.