[OpenSIPS-Users] UPDATE (SDP) modification

2022-11-16 Thread Bela H
Hello, Is there any way to modify the UPDATE (SDP) content, i.e. c=IN IP4 aaa.xx.yyy.zzz The callee is sending this message from the PSTN network and I need to use rtpproxy. Without the UPDATE(SDP) modification the call is one way speech/mute. Cheers, Bela

Re: [OpenSIPS-Users] Mid_Registrar contact

2022-11-16 Thread Liviu Chircu
On 16.11.2022 18:56, nutxase via Users wrote: Is it possible to change the contact on mid_registrar to be the endpoint ip etc as currently when registering to asterisk we see the details of opensips, but i want to hide that and rather show the endpoint is that possible? Hi nutxase, The

Re: [OpenSIPS-Users] OpenSIPS Summit 2023 in USA - is Houston !!!!

2022-11-16 Thread Joseph Jackson
While I was hoping for Dallas at least Houston has way better food than Miami. Joseph From: Users on behalf of johan Sent: Wednesday, November 16, 2022 11:02 AM To: users@lists.opensips.org Subject: Re: [OpenSIPS-Users] OpenSIPS Summit 2023 in USA - is

Re: [OpenSIPS-Users] OpenSIPS Summit 2023 in USA - is Houston !!!!

2022-11-16 Thread johan
isn't it : Houston, we have a problem :-) On 16/11/2022 16:01, Bogdan-Andrei Iancu wrote: The poll closed and we have a winner, *Houston*, the Space City ! In was a tight competition, with ~200 votes from the community side. Many thanks to all who got involved here and helped us in taking the

[OpenSIPS-Users] Mid_Registrar contact

2022-11-16 Thread nutxase via Users
Hi All Is it possible to change the contact on mid_registrar to be the endpoint ip etc as currently when registering to asterisk we see the details of opensips, but i want to hide that and rather show the endpoint is that possible?___ Users mailing

Re: [OpenSIPS-Users] OpenSIPS Summit 2023 in USA - is Houston !!!!

2022-11-16 Thread Bogdan-Andrei Iancu
The poll closed and we have a winner, *Houston*, the Space City ! In was a tight competition, with ~200 votes from the community side. Many thanks to all who got involved here and helped us in taking the decision. The detailed results may be found here [1] Now, we will set everything in

Re: [OpenSIPS-Users] socket_in(port) vs socket_in(advertised_port)

2022-11-16 Thread Ross McKillop via Users
On 16 Nov 2022, at 11:35, Liviu Chircu wrote: > > On 25.10.2022 19:11, Ross McKillop via Users wrote: >> >> I would have expected $socket_in(port) to contain the actual port that was >> used (53235) and $socket_in(advertised_port) to contain the port that is >> advertised as the listening

Re: [OpenSIPS-Users] socket_in(port) vs socket_in(advertised_port)

2022-11-16 Thread Liviu Chircu
On 25.10.2022 19:11, Ross McKillop via Users wrote: I would have expected $socket_in(port) to contain the actual port that was used (53235) and $socket_in(advertised_port) to contain the port that is advertised as the listening port for that socket (e.g. 7700) - however $socket_in(port)