asterisk users - Nov 2007 - Call terminated with error message logged

I just had a SIP call drop out with the following in the logs and would be
interested to know where to start tracking it down if it recurs.


I'm still running svn trunk due to the experiments I was carrying out
earlier
this week to find out whether that port issue had been resolved (which it
hadn't). I will downgrade to 1.4.13 however. This is my home machine, and
nobody else is depending on it.

[Nov  7 20:11:01] WARNING[3486] chan_sip.c: Maximum retries exceeded on
transmission 435ecc4c34d3a4693287e7938d5b9890 at 192.168.0.2 for seqno 212385315
(Critical Response)

On Wed, 2007-11-07 at 20:29 +1100, Jason White wrote:
> [Nov  7 20:11:01] WARNING[3486] chan_sip.c: Maximum retries exceeded
> on transmission 435ecc4c34d3a4693287e7938d5b9890 at 192.168.0.2 for seqno
> 212385315 (Critical Response)
This is usually an indication that Asterisk has tried several times to
send an important message to the device, but it hasn't responded, so
we're giving up trying to talk to it.  If I were you I'd start by doing
a SIP trace and then try to figure out why the phone isn't responding to
Asterisk's messages.

 
-- 
Jared Smith
Community Relations Manager
Digium, Inc.