|
We seem to get these quite frequently - but as far
as I can tell, it also doesn't appear to be causing any major problems as far as
calls are concerned... so thus far I have just ignored them. Are the calls not
actually being terminated properly by the phone, despite the user hanging
up?
We did have a problem with our Cisco phones such
that any simple 'reload' of asterisk would cause a phone not to ring unless it
re-registers - but that seems to be sorted now (for no reason ; I didn't "fix"
anything!).
If you aren't finding any problems with these
errors either... then I would suggest just ignoring them.
- unless anyone could explain what they actually
mean?
Terence
Has anyone ever seen these errors generated by a
cisco 7960? none of our other brand phones seem to generate these
erros:
Jan 27 21:54:07 WARNING[-1147556944]:
chan_sip.c:486 retrans_pkt: Maximum retrie
s exceeded on call [EMAIL PROTECTED]
for seqno 1
01 (Response)
Jan 27 21:54:08 WARNING[-1147556944]:
chan_sip.c:486 retrans_pkt: Maximum retrie
s exceeded on call [EMAIL PROTECTED]
for seqno 1
01 (Response)
Jan 27 21:54:12 WARNING[-1147556944]:
chan_sip.c:486 retrans_pkt: Maximum retrie
s exceeded on call [EMAIL PROTECTED]
for seqno 1
01 (Response)
Jan 27 21:54:14 WARNING[-1147556944]:
chan_sip.c:2485 __transmit_response: Unabl
e to determine sequence number
from ''
Jan 27 21:54:18 WARNING[-1147556944]: chan_sip.c:2485
__transmit_response: Unabl
e to determine sequence number from ''
Jan 27
21:54:22 WARNING[-1147556944]: chan_sip.c:2485 __transmit_response: Unabl
e
to determine sequence number from ''
Thanks! Any feedback would be appreciated
:)
Chris
|
