I do hope not, the network team should be sick of me hammering home not to set up NAT on these routes :D
From: johan de clercq <[email protected]> Date: Monday, 2 February 2026 at 8:59 am To: Alistair Cleminson <[email protected]> Subject: Re: [OpenSIPS-Users] Problems passing BYE signal in v3.7 You don't often get email from [email protected]. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> [CAUTION] This email is from an external sender - Please be cautious, particularly with any links and attachments. If you suspect a phishing email, please report it to IT. 9 out of 10 it will be a NAT problem. On 1/30/26 17:54, Alistair Cleminson wrote: Thanks for the tip, it turns out I'd completely misunderstood the process. This configuration doesn't generate the errors & passes calls: <snip> From: johan de clercq <[email protected]><mailto:[email protected]> Date: Thursday, 29 January 2026 at 9:41 am To: Alistair Cleminson <[email protected]><mailto:[email protected]> Subject: Re: [OpenSIPS-Users] Problems passing BYE signal in v3.7 You don't often get email from [email protected]<mailto:[email protected]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> [CAUTION] This email is from an external sender - Please be cautious, particularly with any links and attachments. If you suspect a phishing email, please report it to IT. maybe changing the 2 vars to avp's will fix the issue. On 1/27/26 17:27, Alistair Cleminson wrote: Hi, I've nearly completed the process of upgrading our ancient v1.7 deployment to v3.6. The new deployment is installed on Ubuntu 24.04 from the OpenSIPS repos. These servers are our inbound hand-off from our upstream supplier, they take a call, inspect the called number element against the database, and then pass it on to the target system with the internal reference or decline the call. <snip>
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
