11 apr 2006 kl. 16.05 skrev Brent Torrenga:
Out internet connection was out this morning. It seems that the SIP
extensions on our LAN were affected. Behavior like:
Call comes in over POTS to a TDM400P, there is a delay then before
the Cisco
79[46]0's start to ring.
If we were lucky enough
If DNS does not work on your local network, Asterisk will lock up.
Out of curiosity - the async implementation you mentioned in the other
thread - will it replace gethostbyname with something smarter or just
run things in a different thread asynchronously?
Thanks,
Cristi
12 apr 2006 kl. 09.08 skrev Cristian Draghici:
If DNS does not work on your local network, Asterisk will lock up.
Out of curiosity - the async implementation you mentioned in the other
thread - will it replace gethostbyname with something smarter or just
run things in a different thread
Out internet connection was out this morning. It seems that the SIP
extensions on our LAN were affected. Behavior like:
Call comes in over POTS to a TDM400P, there is a delay then before the Cisco
79[46]0's start to ring.
If we were lucky enough to get a call through, then we could not transfer
because, a this time, the sip stack doesn't have asynchronous DNS... so ALL the sip code is stucked waiting timeouts for DNS queries (that are long timeouts).
When you try to dial a LAN device, the sip code is trying to resolve your voISP service providers' addresses.
We workaround this putting
I've had this problem too. It would get so bad, that it wouldn't even
answer incoming calls, and if I tried to dial out via pstn, I would
have hung up before it got around to dialing (which it would
eventually do, unfortunately).
A short-short term solution was to install bind, and use it as
Would that caching dns daemon be nscd? (included in every distro).
I had some problem with it in the past and don´t like it, but it´s
major function is to turn a workstation capable of self-caching DNS
and NIS queries.
andre
On 4/11/06, Joseph Tanner [EMAIL PROTECTED] wrote:
I've had this
