Re: [SR-Users] set_advertised_address

Hello, it is not clear what exactly you want to achieve... Is it that for connected phones from local network to use the local IP and for sip messages with devices outside to use external ip? Cheers, Daniel On 04.12.18 23:33, Kjeld Flarup wrote: > Hello > > I have a PBX behind NAT. > Thus I

Re: [SR-Users] is_e164 logic to detect valid number

You might also want to have a look at the “phonenum” module... https://www.kamailio.org/docs/modules/5.2.x/modules/phonenum.html On Tue, Dec 4, 2018 at 19:12 Patrick Wakano wrote: > Thanks for the replies guys! > I will probably add a length test to invalidate too short numbers! > By the way,

Re: [SR-Users] is_e164 logic to detect valid number

Thanks for the replies guys! I will probably add a length test to invalidate too short numbers! By the way, I had a quick look in the ITU recommendation ( https://www.itu.int/rec/T-REC-E.164/en) and looks like the short numbers are for local purposes only being part of the "Non-ITU-T E.164

Re: [SR-Users] set_advertised_address

Sure, eliminate NAT altogether? Haha Don't see how else. On Tue, Dec 4, 2018, 5:34 PM Kjeld Flarup Hello > > I have a PBX behind NAT. > Thus I advertise the public IP, and forwards the port to my PBX. > > listen=LOCALIP:5070 advertise EXTERNALIP:5070 > > Now clients can connect to the PBX from

[SR-Users] set_advertised_address

Hello I have a PBX behind NAT. Thus I advertise the public IP, and forwards the port to my PBX. listen=LOCALIP:5070 advertise EXTERNALIP:5070 Now clients can connect to the PBX from the Internet. And also inside the LAN, because I have enabled NAT loopback. However some customers sysadmins

Re: [SR-Users] Dispatcher clear dst_avp

To answer my own question regarding the reset of the avp variable: avp_delete(name) did the trick. Grant Bagdasarian Senior Developer +31765727054 cm.com [cid:image002.png@01D48BF4.08AB4470] From: sr-users On Behalf Of Grant Bagdasarian Sent: dinsdag 4 december 2018 15:33

[SR-Users] Dispatcher clear dst_avp

Hello, I'm trying to use multiple destination sets which may include the same destination. For instance: SET ID: 1 sip:10.0.0.1:5060 sip:10.0.0.2:5060 SET ID: 2 sip:10.0.0.1:5060 Whenever a new SIP INVITE is sent to the Kamailio instance it will use SET ID 1. If then for some reason this call

Re: [SR-Users] Auth_xkeys module - freeing already freed pointer

Hello, can you try with master branch or with the patch from the next commit?   - https://github.com/kamailio/kamailio/commit/01f5ecbc45c236daea62d6638a02c168720c8479 If all is ok, I will backport. Cheers, Daniel On 04.12.18 10:12, José Seabra wrote: > Hello Henning, > > The function that

Re: [SR-Users] xlog issue

Hello, typically syslog has some rate limiting, and with centos, you get extra limits with selinux. You have to dive into rsyslog, system config and selinux. What you can do is to start with log_stderror=yes (or -E command line option) and see if it is printing the messages you are looking for

Re: [SR-Users] xlog issue

Hello, Actually, async Syslog option was the initial option which I tried - it wasn't working properly so I changed to a synchronous mode in the hope that it will work better, but unfortunately it didn't. >Daniel-Constantin Mierla : > >Hello, > >try with async syslogging option in >

Re: [SR-Users] Auth_xkeys module - freeing already freed pointer

Hello Henning, The function that seems to be causing this is "auth_xkeys_add". Let me know if do you need something else. Thank you for the support José Henning Westerholt escreveu no dia segunda, 3/12/2018 à(s) 21:59: > Am Montag, 3. Dezember 2018, 19:03:36 CET schrieb José Seabra: > > I'm

Re: [SR-Users] xlog issue

Hello, try with async syslogging option in rsyslog config: add a - in front of the file name, like: local0.*             -/var/log/kamailio/kamailio.log See if the results are better. Cheers, Daniel On 02.12.18 16:14, Soltanici Ilie wrote: > > Hello, > > I have a strange situation by using

Re: [SR-Users] presence/mwi issue

For the records, the commit was just backported to branch 5.1. Cheers, Daniel On 28.11.18 17:29, Daniel-Constantin Mierla wrote: > Hello, > > what I actually said it was that if you backport to your local git clone > and testing was ok, then you can push it to 5.1 branch by yourself, no > need

Re: [SR-Users] Dispatcher with a naptr address as destination

I just did it, if you use git, you can pull and have it. Nightly built Debian packages will make it available tomorrow if you use deb.kamailio.org apt repository with nightly builds. Cheers, Daniel On 03.12.18 11:37, Patrick Murphy wrote: > Thanks for the fix Daniel, > > Any ETA on when this