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 complains that NAT loopback is a security risk. I have not been able to find any exploits of this, but the sales and support people asks if it is possible to remove this NAT loopback requirement.
I could look at $rd and if it is local, then I could advertise LOCALIP. I found set_advertised_address("LOCALIP");
set_advertised_address however only seems to modify the latest Via header, not the Record-route, and audio neither works.
Could I do something to make this work, or is it a dead end?
Sure, eliminate NAT altogether? Haha
Don't see how else.
On Tue, Dec 4, 2018, 5:34 PM Kjeld Flarup <kjeld.flarup@liberalismen.dk wrote:
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 complains that NAT loopback is a security risk. I have not been able to find any exploits of this, but the sales and support people asks if it is possible to remove this NAT loopback requirement.
I could look at $rd and if it is local, then I could advertise LOCALIP. I found set_advertised_address("LOCALIP");
set_advertised_address however only seems to modify the latest Via header, not the Record-route, and audio neither works.
Could I do something to make this work, or is it a dead end?
-- -------------------- 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 ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
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 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 complains that NAT loopback is a security risk. I have not been able to find any exploits of this, but the sales and support people asks if it is possible to remove this NAT loopback requirement.
I could look at $rd and if it is local, then I could advertise LOCALIP. I found set_advertised_address("LOCALIP");
set_advertised_address however only seems to modify the latest Via header, not the Record-route, and audio neither works.
Could I do something to make this work, or is it a dead end?
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 ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk
On 12/5/18 8:40 AM, Daniel-Constantin Mierla wrote:
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 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 complains that NAT loopback is a security risk. I have not been able to find any exploits of this, but the sales and support people asks if it is possible to remove this NAT loopback requirement.
I could look at $rd and if it is local, then I could advertise LOCALIP. I found set_advertised_address("LOCALIP");
set_advertised_address however only seems to modify the latest Via header, not the Record-route, and audio neither works.
Could I do something to make this work, or is it a dead end?
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.
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 ---------------------- Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk
On 12/5/18 12:11 PM, Daniel Tryba wrote:
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.
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
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 based on local traffic, most devices support so called outbound proxy address, you can set that to the sip server address with ip.
Cheers, Daniel
On 05.12.18 13:02, Kjeld Flarup wrote:
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 ---------------------- Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk
On 12/5/18 12:11 PM, Daniel Tryba wrote:
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.
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
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 miconda@gmail.com wrote:
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 based on local traffic, most devices support so called outbound proxy address, you can set that to the sip server address with ip.
Cheers, Daniel
On 05.12.18 13:02, Kjeld Flarup wrote:
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 ---------------------- Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk
On 12/5/18 12:11 PM, Daniel Tryba wrote:
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.
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
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 is quite common in enterprise environment, the devices on local network connect by private IP, and the external devices connect to the firewall ip and this one does port forwarding.
Cheers, Daniel
On 05.12.18 16:56, Sergiu Pojoga wrote:
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 <miconda@gmail.com mailto:miconda@gmail.com> wrote:
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 based on local traffic, most devices support so called outbound proxy address, you can set that to the sip server address with ip. Cheers, Daniel On 05.12.18 13:02, Kjeld Flarup wrote: > 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 ---------------------- > Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog > Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 > Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk <http://www.liberalismen.dk> > > On 12/5/18 12:11 PM, Daniel Tryba wrote: >> 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. >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com> _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
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 miconda@gmail.com wrote:
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 is quite common in enterprise environment, the devices on local network connect by private IP, and the external devices connect to the firewall ip and this one does port forwarding.
Cheers, Daniel On 05.12.18 16:56, Sergiu Pojoga wrote:
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 miconda@gmail.com wrote:
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 based on local traffic, most devices support so called outbound proxy address, you can set that to the sip server address with ip.
Cheers, Daniel
On 05.12.18 13:02, Kjeld Flarup wrote:
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 ---------------------- Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 Den ikke akademiske hjemmeside for liberalismen -
www.liberalismen.dk
On 12/5/18 12:11 PM, Daniel Tryba wrote:
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.
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
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 Linux could perhaps dictate which connection to use.
-------------------- 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 ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk
On 12/5/18 6:10 PM, Sergiu Pojoga wrote:
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 <miconda@gmail.com mailto:miconda@gmail.com> wrote:
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 is quite common in enterprise environment, the devices on local network connect by private IP, and the external devices connect to the firewall ip and this one does port forwarding. Cheers, Daniel On 05.12.18 16:56, Sergiu Pojoga wrote: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 <miconda@gmail.com <mailto:miconda@gmail.com>> wrote: 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 based on local traffic, most devices support so called outbound proxy address, you can set that to the sip server address with ip. Cheers, Daniel On 05.12.18 13:02, Kjeld Flarup wrote: > 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 ---------------------- > Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog > Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 > Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk <http://www.liberalismen.dk> > > On 12/5/18 12:11 PM, Daniel Tryba wrote: >> 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. >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com> _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users-- Daniel-Constantin Mierla --www.asipto.com <http://www.asipto.com> www.twitter.com/miconda <http://www.twitter.com/miconda> --www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Kamailio World Conference --www.kamailioworld.com <http://www.kamailioworld.com> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin --www.asipto.com <http://www.asipto.com>
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
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 provider via a trunk or so, you can set the socket to be used for outgoing leg via $fs/force_send_sock()/set_send_sock(). Some modules such as dispatcher have also the option to set the outgoing socket...
Cheers, Daniel
On 05.12.18 23:04, Kjeld Flarup wrote:
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 Linux could perhaps dictate which connection to use.
-------------------- 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 ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk
On 12/5/18 6:10 PM, Sergiu Pojoga wrote:
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 <miconda@gmail.com mailto:miconda@gmail.com> wrote:
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 is quite common in enterprise environment, the devices on local network connect by private IP, and the external devices connect to the firewall ip and this one does port forwarding. Cheers, Daniel On 05.12.18 16:56, Sergiu Pojoga wrote: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 <miconda@gmail.com <mailto:miconda@gmail.com>> wrote: 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 based on local traffic, most devices support so called outbound proxy address, you can set that to the sip server address with ip. Cheers, Daniel On 05.12.18 13:02, Kjeld Flarup wrote: > 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 ---------------------- > Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog > Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 > Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk <http://www.liberalismen.dk> > > On 12/5/18 12:11 PM, Daniel Tryba wrote: >> 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. >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com> _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users-- Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com>
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-
Daniel Tryba -
Daniel-Constantin Mierla -
Kjeld Flarup -
Sergiu Pojoga