Hi Kamlesh,
I would suspect you do something wrong in the failure_route, when
handling the FWD cases. Maybe another change over the contact hdr in the
INVITE ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit, Amsterdam, May 2020
https://www.opensips.org/events/Summit-2020Amsterdam/
On 4/11/20 3:51 PM, Kamlesh . wrote:
Hello Team,
I have a problem with TOPOLOGY HIDING and NAT issues while using
forwarding on busy/no-answer. I fix the NATed contact and then create
dialog with topology hiding. The UPSTREAM (callee to caller) BYE
relays to private IP instead of public. All the previous requests
relay after fixing the contact. This only happens when a call is
forwarded on BUSY/NO ANSWER Relay the packetsto opensips itself, We
just change the request number and add some required headers to detect
the forwarded request. So the all dialog related things are the same
for both the request one is initial request and forwarded request.
Anyone can help me to short out this issue. I’m ready to provide other
information if any to solve the issue.
Regards,
Kamlesh
Disclaimer :
This e-mail and any file transmitted with it are for exclusive use of
the intended recipient(s)
and may contain confidential and privileged information. If you are
not the intended recipient,
please contact the sender by replying this e-mail and destroy all
copies and original message.
Any unauthorized review,use, disclosure, dissemination, forwarding,
printing and copying of this
email or any action taken in reliance of this e-mail is strictly
prohibited and may be unlawful.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
