Re: [OpenSIPS-Users] OPUS transcoding query

Thanks very much for your reply. There's a lot to consider but it's really helpful On Wed, 21 Jul 2021, 18:27 Gregory Massel, wrote: > A few factors to consider: > > *1. Quality* > > 1.1. If you transcode to PCMU using RTPengine, you will lose the wideband > audio quality benefits of Opus. By

Re: [OpenSIPS-Users] OPUS transcoding query

A few factors to consider: _1. Quality_ 1.1. If you transcode to PCMU using RTPengine, you will lose the wideband audio quality benefits of Opus. By contrast, if Asterisk accepts the calls using Opus, it will transcode internally to sln16 for purposes of media processing (playing IVRs,

[OpenSIPS-Users] OpenSIPS 3.2.0 LTS goes stable

OpenSIPS 3.2.0 LTS goes from beta to stable *It got stable!* There were like two months of work, of testing, of reporting and of fixing, but we did it! The OpenSIPS 3.2 release passed all the tests and exams and now it is

Re: [OpenSIPS-Users] add_path_received and TLS - received address problem

On 21.07.2021 17:47, Mark Allen wrote: I'm seeing errors for pinger OPTIONS and Asterisk NOTIFY SIP messages going out to the NATed TLS UAC... ERROR:core:unescape_user: invalid hex digit <37> ERROR:path:path_rr_callback: failed to unescape received=sip:35.x.x.x:60026%%3btransport%%3dtls The

Re: [OpenSIPS-Users] add_path_received and TLS - received address problem

Hi Liviu - thanks for getting back to me. I'm seeing errors for pinger OPTIONS and Asterisk NOTIFY SIP messages going out to the NATed TLS UAC... ERROR:core:unescape_user: invalid hex digit <37> ERROR:path:path_rr_callback: failed to unescape received=sip:35.x.x.x:60026%%3btransport%%3dtls

[OpenSIPS-Users] Opensips CP Permissions "RELOAD on SERVER" produces error

Opensips 3.1.2 CP 8.3.1 Debian 10 When adding permissions, I hit "Reload on Server" but I get the following error: Sending to *json:127.0.0.1:/mi * : MI command failed with code -32601 (Method not found) I I don't get this error on any other page but this one when

Re: [OpenSIPS-Users] add_path_received and TLS - received address problem

On 20.07.2021 13:26, Mark Allen wrote: On registration add_path_received() works but the received address is not formatted correctly. I am seeing '%%3b' instead of a semicolon, and '%%3d' instead of an equals sign. Hi Mark, How exactly is this peculiar formatting breaking your logic?