[SR-Users] Re: Standard on RTP ports
On 15/12/2023 14.04, [EXT] Calvin E. via sr-users wrote: Probably this: https://github.com/sipwise/rtpengine/blob/master/debian/changelog ngcp-rtpengine (12.1.0.0+0~mr12.1.0.0) unstable; urgency=medium * [2fa121c] MT#54294 add GPU support * [b3544be] MT#54294 packaging for rtpengine-gpu * [079bfac] MT#55283 fix up pkg generator for -gpu packages I'm guessing this uses underlying FFmpeg CUDA support. It's a bit more complicated than this as ffmpeg doesn't have GPU support for audio processing. So we took the Opus codec, ported it to CUDA, heavily modified it for parallel execution, and combined it with some other codecs (G.711 for now) to be able to do transcoding on a GPU. This isn't relevant for the regular media proxy (RTP passthrough) use case though. Cheers __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: Regretfully we were unable to process the URI
Hi Gavin,
This error is generated internally when trying to relay the message. A useful
troubleshooting step would be to add a line that prints the Request URI to
console before this happens, but subsequent to the registration lookup (if
you're using a registrar, and I presume you are):
xinfo("[$ci] Final request URI is: $ru\n");
I think this would add some insight.
-- Alex
> On 16 Dec 2023, at 09:33, Gavin Baumanis via sr-users
> wrote:
>
> Hi Everyone,
>
> Very new to SIP
> And to Kamailio Configuration / administration.
>
> I have a working AWS instance with Kamailio installed on it - and it works
> fine.
>
> We are creating a whole new environment and I have cloned the existing AWS
> EC2 instances.
> I have edited all the configs to ensure that they are using the correct DNS
> names and / or IP addresses.
> Otherwise the "configs" are identical.
>
> While attempting to call a SIP number, I get the following message, returned
> to the soft phone I am using (microSIP)
> Regretfully we were unable to process the URI (479/SL)
>
> I can also see the same error message in the console of the Kamailio server.
>
> I am hoping that this might mean something to someone enough - to suggest
> some troubleshooting steps, please.
>
> Thanks;
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the
> sender!
> Edit mailing list options or unsubscribe:
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Regretfully we were unable to process the URI
Hi Everyone, Very new to SIP And to Kamailio Configuration / administration. I have a working AWS instance with Kamailio installed on it - and it works fine. We are creating a whole new environment and I have cloned the existing AWS EC2 instances. I have edited all the configs to ensure that they are using the correct DNS names and / or IP addresses. Otherwise the "configs" are identical. While attempting to call a SIP number, I get the following message, returned to the soft phone I am using (microSIP) *Regretfully we were unable to process the URI (479/SL)* I can also see the same error message in the console of the Kamailio server. I am hoping that this might mean something to someone enough - to suggest some troubleshooting steps, please. Thanks; __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
