[asterisk-users] Codec Negotiation

Douglas Garstang dgarstang at oneeighty.com
Fri Jul 21 13:07:37 MST 2006


> -----Original Message-----
> From: Joshua Colp [mailto:jcolp at digium.com]
> Sent: Friday, July 21, 2006 9:38 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [asterisk-users] Codec Negotiation
> 
> 
> ----- Original Message -----
> From: Douglas Garstang
> [mailto:dgarstang at oneeighty.com]
> To: olivier.taylor at phonext.com, Asterisk
> Users Mailing List - Non-Commercial Discussion
> [mailto:asterisk-users at lists.digium.com]
> Sent: Fri, 21 Jul 2006 16:21:15
> -0300
> Subject: RE: [asterisk-users] Codec Negotiation
> 
> 
> > Well, I wish someone would tell Kevin Fleming that.
> > 
> 
> So... the realtime architecture can work when shared between 
> servers - but not all the time, and it depends on certain 
> variables.  Multiple servers can grab the same information 
> from the database, but it doesn't mean they will be able to 
> contact the phone for example. This is what Kevin was talking 
> about. If a phone is behind NAT and registers to one Asterisk 
> machine, the device doing the NAT will setup in it's memory a 
> mapping of the external port to the internal IP+port. 
> Depending on the implementation and setup, only the server 
> that the phone registered to will be able to send packets 
> back. Thus if you have failover to another server for 
> example, that server will not be able to contact the phone.
> 
> Like I said, there's too many variables to make it work all 
> the time...
> 
> Now - you can pull information in order for them to be able 
> to place calls. That should be fine.

Don't know about that. I'm not sure why he brought NAT up, as I didn't mention it. Might be a red herring I think.



More information about the asterisk-users mailing list