Re: [SR-Users] set_advertised_address

2018-12-05 Thread Daniel-Constantin Mierla
When a phone registers, its traffic comes to one of the two sockets. When that phone is called, after lookup location, the socket associated to the registration of the target user is selected. So you do not need to do anything special for calling between phones. When calling to a PSTN/foreign

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

2018-12-05 Thread Patrick Wakano
Thanks for the hint Joel! That's a really nice addition! One more good reason to upgrade to version 5.2!! Cheers, Patrick Wakano On Wed, 5 Dec 2018 at 14:30, Joel Serrano wrote: > You might also want to have a look at the “phonenum” module... > >

Re: [SR-Users] set_advertised_address

2018-12-05 Thread Kjeld Flarup
So I could do something like this: listen=192.168.2.9:5070 advertise 20.30.40.50:5070 listen=192.168.2.9:5050 However when I do an invite to 192.168.2.32, would Kamailio choose 5050 or 5070? Same when inviting to 40.40.40.40 If I were to listen to another local IP, then the routing table in

Re: [SR-Users] set_advertised_address

2018-12-05 Thread Sergiu Pojoga
For whatever reason my initial impression was if it was possible for external devices to connect without port forwarding... I stand corrected. On Wed, Dec 5, 2018 at 11:30 AM Daniel-Constantin Mierla wrote: > It is not about an external network interface, but external > traffic/devices. The

Re: [SR-Users] set_advertised_address

2018-12-05 Thread Daniel-Constantin Mierla
It is not about an external network interface, but external traffic/devices. The NAT in this case is a port forwarding firewall, like Amazon or Google cloud, where you have a local address on server and the firewall is forwarding by port all traffic from an assigned public address. Such scenario

Re: [SR-Users] set_advertised_address

2018-12-05 Thread Sergiu Pojoga
Slightly confused here... didn't he say that Kamailio and PBX are behind NAT? If so, what external interface are we talking about? On Wed, Dec 5, 2018 at 9:18 AM Daniel-Constantin Mierla wrote: > Hello, > > you do not need a second kamailio, the same instance can listen on > multiple sockets.

Re: [SR-Users] set_advertised_address

2018-12-05 Thread Daniel-Constantin Mierla
Hello, you do not need a second kamailio, the same instance can listen on multiple sockets. You can also use a single ip, just listen on one port for traffic from local network and on another port for external traffic (this socket with advertise address). If the router cannot handle dns query

Re: [SR-Users] set_advertised_address

2018-12-05 Thread Kjeld Flarup
That might work, provided that the router can handle a local DNS. It would, however still require adding an extra Kamailio instance with another IP. Plus a branch of the invite to both local and public instance. Plus an extra location table. Med Liberalistiske Hilsner

Re: [SR-Users] set_advertised_address

2018-12-05 Thread Daniel Tryba
On Wed, Dec 05, 2018 at 09:40:38AM +0100, Kjeld Flarup wrote: > Yes, the Phones may be on either local LAN (Wifi) and Internet via mobile > data. How about use different local address, 1 with an advertise for external clients, 1 without. Have local DNS resolv to the 1 ip without advertise.

Re: [SR-Users] set_advertised_address

2018-12-05 Thread Kjeld Flarup
Hi Daniel Yes, the Phones may be on either local LAN (Wifi) and Internet via mobile data. Med Liberalistiske Hilsner -- Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 Den