Hi!
I have an interface which is an alias in Linux that I want Kamailio to listen to. The interface name is eth0:p01
I've tried with
listen=udp:eth0:p01:5080 listen=eth0:p01:5080 listen=eth0:p01
Kamailio doesn't accept this syntax. Claims "syntax error" and " ip address, interface name or hostname expected".
Since this way of naming interfaces is common in Linux, I think we should support it. Or? Is there a way - are quotation marks allowed here?
Cheers, /O
Hello Olle,
Couldn't you get around this by just specifying the IP address of the interface? e.g.
listen=udp:xxx.xxx.xxx.xxx:5060
-- Alex
On 06/04/2014 04:34 PM, Olle E. Johansson wrote:
Hi!
I have an interface which is an alias in Linux that I want Kamailio to listen to. The interface name is eth0:p01
I've tried with
listen=udp:eth0:p01:5080 listen=eth0:p01:5080 listen=eth0:p01
Kamailio doesn't accept this syntax. Claims "syntax error" and " ip address, interface name or hostname expected".
Since this way of naming interfaces is common in Linux, I think we should support it. Or? Is there a way - are quotation marks allowed here?
Cheers, /O _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 04 Jun 2014, at 22:35, Alex Balashov abalashov@evaristesys.com wrote:
Hello Olle,
Couldn't you get around this by just specifying the IP address of the interface? e.g.
listen=udp:xxx.xxx.xxx.xxx:5060
Not in this configuration, but with some tweaking I may. But it would simplify a lot if I just could point to the interface.
/O
-- Alex
On 06/04/2014 04:34 PM, Olle E. Johansson wrote:
Hi!
I have an interface which is an alias in Linux that I want Kamailio to listen to. The interface name is eth0:p01
I've tried with
listen=udp:eth0:p01:5080 listen=eth0:p01:5080 listen=eth0:p01
Kamailio doesn't accept this syntax. Claims "syntax error" and " ip address, interface name or hostname expected".
Since this way of naming interfaces is common in Linux, I think we should support it. Or? Is there a way - are quotation marks allowed here?
Cheers, /O _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Alex Balashov - Principal Evariste Systems LLC Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Please be kind to the English language:
http://www.entrepreneur.com/article/232906
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 06/04/2014 04:37 PM, Olle E. Johansson wrote:
On 04 Jun 2014, at 22:35, Alex Balashov abalashov@evaristesys.com wrote:
Hello Olle,
Couldn't you get around this by just specifying the IP address of the interface? e.g.
listen=udp:xxx.xxx.xxx.xxx:5060
Not in this configuration, but with some tweaking I may. But it would simplify a lot if I just could point to the interface.
I run into this problem a lot, too, with eth0:x subinterfaces. But specifying the address is the only way I know of to solve it at present.
On 04 Jun 2014, at 22:38, Alex Balashov abalashov@evaristesys.com wrote:
On 06/04/2014 04:37 PM, Olle E. Johansson wrote:
On 04 Jun 2014, at 22:35, Alex Balashov abalashov@evaristesys.com wrote:
Hello Olle,
Couldn't you get around this by just specifying the IP address of the interface? e.g.
listen=udp:xxx.xxx.xxx.xxx:5060
Not in this configuration, but with some tweaking I may. But it would simplify a lot if I just could point to the interface.
I run into this problem a lot, too, with eth0:x subinterfaces. But specifying the address is the only way I know of to solve it at present.
I guess it's about time to file a bug report :-)
/O
On 05/06/14 07:31, Olle E. Johansson wrote:
On 04 Jun 2014, at 22:38, Alex Balashov abalashov@evaristesys.com wrote:
On 06/04/2014 04:37 PM, Olle E. Johansson wrote:
On 04 Jun 2014, at 22:35, Alex Balashov abalashov@evaristesys.com wrote:
Hello Olle,
Couldn't you get around this by just specifying the IP address of the interface? e.g.
listen=udp:xxx.xxx.xxx.xxx:5060
Not in this configuration, but with some tweaking I may. But it would simplify a lot if I just could point to the interface.
I run into this problem a lot, too, with eth0:x subinterfaces. But specifying the address is the only way I know of to solve it at present.
I guess it's about time to file a bug report :-)
I haven't checked the grammar for listen value, but have you tried to enclose the interface name in between double quotes? Cheers, Daniel
On 05 Jun 2014, at 08:11, Daniel-Constantin Mierla miconda@gmail.com wrote:
On 05/06/14 07:31, Olle E. Johansson wrote:
On 04 Jun 2014, at 22:38, Alex Balashov abalashov@evaristesys.com wrote:
On 06/04/2014 04:37 PM, Olle E. Johansson wrote:
On 04 Jun 2014, at 22:35, Alex Balashov abalashov@evaristesys.com wrote:
Hello Olle,
Couldn't you get around this by just specifying the IP address of the interface? e.g.
listen=udp:xxx.xxx.xxx.xxx:5060
Not in this configuration, but with some tweaking I may. But it would simplify a lot if I just could point to the interface.
I run into this problem a lot, too, with eth0:x subinterfaces. But specifying the address is the only way I know of to solve it at present.
I guess it's about time to file a bug report :-)
I haven't checked the grammar for listen value, but have you tried to enclose the interface name in between double quotes?
fix_hostname(): ERROR: fix_hostname: could not resolve eth0:0
listen=udp:"eth0:0":5080 listen="eth0:0"
/O
On 05/06/14 08:18, Olle E. Johansson wrote:
On 05 Jun 2014, at 08:11, Daniel-Constantin Mierla miconda@gmail.com wrote:
On 05/06/14 07:31, Olle E. Johansson wrote:
On 04 Jun 2014, at 22:38, Alex Balashov abalashov@evaristesys.com wrote:
On 06/04/2014 04:37 PM, Olle E. Johansson wrote:
On 04 Jun 2014, at 22:35, Alex Balashov abalashov@evaristesys.com wrote:
Hello Olle,
Couldn't you get around this by just specifying the IP address of the interface? e.g.
listen=udp:xxx.xxx.xxx.xxx:5060
Not in this configuration, but with some tweaking I may. But it would simplify a lot if I just could point to the interface.
I run into this problem a lot, too, with eth0:x subinterfaces. But specifying the address is the only way I know of to solve it at present.
I guess it's about time to file a bug report :-)
I haven't checked the grammar for listen value, but have you tried to enclose the interface name in between double quotes?
fix_hostname(): ERROR: fix_hostname: could not resolve eth0:0
listen=udp:"eth0:0":5080 listen="eth0:0"
So it is trying to lookup up only as hostname, perhaps is not going to be hard to extend to search it as interface.
Cheers, Daniel
On 05 Jun 2014, at 08:21, Daniel-Constantin Mierla miconda@gmail.com wrote:
On 05/06/14 08:18, Olle E. Johansson wrote:
On 05 Jun 2014, at 08:11, Daniel-Constantin Mierla miconda@gmail.com wrote:
On 05/06/14 07:31, Olle E. Johansson wrote:
On 04 Jun 2014, at 22:38, Alex Balashov abalashov@evaristesys.com wrote:
On 06/04/2014 04:37 PM, Olle E. Johansson wrote:
On 04 Jun 2014, at 22:35, Alex Balashov abalashov@evaristesys.com wrote:
> Hello Olle, > > Couldn't you get around this by just specifying the IP address of the interface? e.g. > > listen=udp:xxx.xxx.xxx.xxx:5060 Not in this configuration, but with some tweaking I may. But it would simplify a lot if I just could point to the interface.
I run into this problem a lot, too, with eth0:x subinterfaces. But specifying the address is the only way I know of to solve it at present.
I guess it's about time to file a bug report :-)
I haven't checked the grammar for listen value, but have you tried to enclose the interface name in between double quotes?
fix_hostname(): ERROR: fix_hostname: could not resolve eth0:0
listen=udp:"eth0:0":5080 listen="eth0:0"
So it is trying to lookup up only as hostname, perhaps is not going to be hard to extend to search it as interface.
Hint: A hostname never has a colon inside.
/O