Hi,
I'm pretty sure you'll need to write domain-translation rules (custom
logic) in order to allow inter-domain calls. There can be many ways to do
that but lets stick to old-school-approach...prefixes. Use prefixes to
differentiate if user want to do inter-domain calling.
Prefix: Domain
1 :
Hello again!
I am happy to announce you that the two new OpenSIPS minor release 2.2.6
and 2.3.3 are now out!
After several months of spinning OpenSIPS in production environments we
managed to track down and fix various bugs. You can find a full list of
changes here:
* OpenSIPS 2.3.3
Hi Royee,
Unfortunately, 2.1 is under the "unmaintained" status for well over a
year now. I highly recommend considering an upgrade to 2.2.5 LTS - it
has almost 2 absolute years worth of community usage and fixes, and we
will roughly support it for almost another two. The differences are
Dear Sir/Madam
We are using multiple SIP domains in one OpenSIPS instance, for example
1...@aaa.com
2...@bbb.com
Both extensions register with the same OpenSIPS, if 1...@aaa.com want to call
2...@bbb.com, the SIP URI the phone sent out will be 2...@aaa.com, how to
configure in confit file to
Hi, John!
Those errors are reported by the RTPProxy server, and depending on the
error, they can be handled by opensips.
In your case, the errors 71 and 72 are reported by RTPProxy when it can
not create UDP listeners for media. Usually these errors are triggered
when rtpproxy runs out of
Hi all,
In light of the recent FreeSWITCH integration enhancements for OpenSIPS
2.4 LTS, I have written a blog piece [1] explaining what they are and
what we can build with them. Enjoy!
Best regards,
[1]:
Hi everyone,
Yesterday we experienced some bad behavior with opensips in a couple of our
production servers. What we saw is that all TLS/TCP connections were
closing and registrations were failing until we restarted opensips. We
can't understand why this happened. CPU metrics seem fine.
We are
