asterisk users - Mar 2006 - Annoying Asterisk Realtime Limitation

Well, this is a major pain in the ass.

I got realtime static working for sip.conf. 'Great!' I thought. That was
until I realised I couldn't use it.

Our Asterisk systems are using OSPF and listen on interface lo:1. Asterisk
doesn't like to use an interface name for it's bindaddr setting, so you
have to put the IP address of lo:1 in there. If you put in 0.0.0.0, it seems to
listen on the first interface it finds, probably eth0. You can't do that
with OSPF because it's load balancing and traffic can come over eth1
instead.

If you point all your Asterisk systems to a single table for sip.conf, what do
you put in the binaddr setting? You can't use the systems IP address at
lo:1, because they're all different, and you can't use 0.0.0.0 or lo:1.
The only solution is to have one sip.conf table for every Asterisk system... 5
in our case.

Anyway, so I went back to a plain text file for sip.conf. What a dissapointment.

Doug.

On 19 Mar 2006, at 17:56, Douglas Garstang wrote:
> Well, this is a major pain in the ass.
>
> I got realtime static working for sip.conf. 'Great!' I thought.  
> That was until I realised I couldn't use it.
>
> Our Asterisk systems are using OSPF and listen on interface lo:1.  
> Asterisk doesn't like to use an interface name for it's bindaddr  
> setting, so you have to put the IP address of lo:1 in there. If you  
> put in 0.0.0.0, it seems to listen on the first interface it finds,  
> probably eth0. You can't do that with OSPF because it's load  
> balancing and traffic can come over eth1 instead.
>
> If you point all your Asterisk systems to a single table for  
> sip.conf, what do you put in the binaddr setting? You can't use the  
> systems IP address at lo:1, because they're all different, and you  
> can't use 0.0.0.0 or lo:1. The only solution is to have one  
> sip.conf table for every Asterisk system... 5 in our case.
At the risk of stirring up a flame war.....

If you have a 'real' database you could work around that problem with  
a view. The view could be
written to pass back a different value of bindaddr depending on which  
client asks, but all the other
values come straight out of base table that is the same for all clients.

A bind addr of 0.0.0.0 should listen on all interfaces that are up at  
the time the listen is
started, I guess your problem is with the source address in the  
outgoing (from asterisk)
reply packets.
>
> Anyway, so I went back to a plain text file for sip.conf. What a  
> dissapointment.
I do think there might have been a work around available there.
>
> Doug.
>

Tim Panton
tim@mexuar.com

No flames here as I realize that there are plenty of limitations with MySQL,
but if you're using the current GA of it views is not one of them.

Regards,
- Brad

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Tim Panton
Sent: Sunday, March 19, 2006 4:15 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Annoying Asterisk Realtime Limitation



On 19 Mar 2006, at 17:56, Douglas Garstang wrote:
> Well, this is a major pain in the ass.
>
> I got realtime static working for sip.conf. 'Great!' I thought.
> That was until I realised I couldn't use it.
>
> Our Asterisk systems are using OSPF and listen on interface lo:1.
> Asterisk doesn't like to use an interface name for it's bindaddr  
> setting, so you have to put the IP address of lo:1 in there. If you  
> put in 0.0.0.0, it seems to listen on the first interface it finds,  
> probably eth0. You can't do that with OSPF because it's load  
> balancing and traffic can come over eth1 instead.
>
> If you point all your Asterisk systems to a single table for
> sip.conf, what do you put in the binaddr setting? You can't use the  
> systems IP address at lo:1, because they're all different, and you  
> can't use 0.0.0.0 or lo:1. The only solution is to have one  
> sip.conf table for every Asterisk system... 5 in our case.
At the risk of stirring up a flame war.....

If you have a 'real' database you could work around that problem with  
a view. The view could be
written to pass back a different value of bindaddr depending on which  
client asks, but all the other
values come straight out of base table that is the same for all clients.

A bind addr of 0.0.0.0 should listen on all interfaces that are up at  
the time the listen is
started, I guess your problem is with the source address in the  
outgoing (from asterisk)
reply packets.
>
> Anyway, so I went back to a plain text file for sip.conf. What a
> dissapointment.
I do think there might have been a work around available there.
>
> Doug.
>

Tim Panton
tim@mexuar.com



_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users



The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

<snip>
> Anyway, so I went back to a plain text file for
> sip.conf. What a dissapointment.
</snip>

This is kind of backwards but you can make a script
that will pull all the info from the DB and save it as
sip.conf. 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com