[Home]

Summary:ASTERISK-02294: New Error Messages (Also Left Calls)
Reporter:bfranks (bfranks)Labels:
Date Opened:2004-08-30 08:33:31Date Closed:2011-06-07 14:10:36
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I just upgraded CVS last night as of CVS-HEAD-08/29/04-20:30:26, and am beginning to see a lot of the error messages pasted below in the Additional Information section.  Additionally, if I do a sip show channels, I see the channels the error logs contain.

A sip show channels yields this:

hunpbx*CLI> sip show channels
Peer             User/ANR    Call ID      Seq (Tx/Rx)   Format
10.10.60.4       2131        fb1f9c7e-20  00101/00002   ULAW
10.10.60.14      2126        e4bf5c80-e4  00101/00002   ULAW
10.10.60.16      (None)      6fa6b5c0208  00101/00002   UNKN
10.10.60.9       (None)      034cb51b7d2  00101/00004   UNKN
10.10.60.16      (None)      7daa434f2d4  00101/00002   UNKN
10.10.60.9       (None)      419bd02f2eb  00101/00004   UNKN
6 active SIP channel(s)
hunpbx*CLI> sip show channel 6fa6b5c02082fcd9329ce282282a3dfa@10.10.10.1
hunpbx*CLI>
 * SIP Call
 Direction:              Incoming
 Call-ID:                6fa6b5c02082fcd9329ce282282a3dfa@10.10.10.1
 Our Codec Capability:   524300
 Non-Codec Capability:   1
 Their Codec Capability:   0
 Joint Codec Capability:   0
 Format                  UNKN
 Theoretical Address:    10.10.60.16:5060
 Received Address:       10.10.60.16:5060
 NAT Support:            RFC3581
 Our Tag:                1031890425
 Their Tag:              59CF1317-CAEF1DE0
 SIP User agent:         PolycomSoundPointIP-SPIP_500-UA/1.1.0
 Need Destroy:           0
 Last Message:           Rx: REFER
 Promiscuous Redir:      No
 Route:                  N/A
 DTMF Mode:              rfc2833

Not sure how to classify this bug, however I know it was not happening in the CVS version from June 10th.


****** ADDITIONAL INFORMATION ******

The /var/log/asterisk/messages log file shows this:

Aug 30 08:18:06 NOTICE[1087093440]: Supervised transfer requested, but unable to find callid 'ac5dc8c9-9c01d3e7-ec2ad82e@10.10.60.9'
Aug 30 08:18:12 WARNING[1087093440]: Maximum retries exceeded on call 419bd02f2ebcd4144489a70a569861cc@10.10.10.1 for seqno 0 (Non-critical Re
sponse)
Aug 30 08:40:13 NOTICE[1087093440]: Supervised transfer requested, but unable to find callid 'e4ba6790-c833ffaa-e2701487@10.10.60.16'
Aug 30 08:40:19 WARNING[1087093440]: Maximum retries exceeded on call 7daa434f2d4bc6a808e3a4ef1b6c07dd@10.10.10.1 for seqno 0 (Non-critical Re
sponse)
Aug 30 08:40:55 NOTICE[1087093440]: Supervised transfer requested, but unable to find callid '13b9cd51-280bf12f-5e810cd6@10.10.60.9'
Aug 30 08:41:01 WARNING[1087093440]: Maximum retries exceeded on call 034cb51b7d25a5162bfce5d62f6d59a9@10.10.10.1 for seqno 0 (Non-critical Re
sponse)
Aug 30 09:19:37 NOTICE[1087093440]: Supervised transfer requested, but unable to find callid '3f65e74c-76c1f586-45e57673@10.10.60.16'
Aug 30 09:19:43 WARNING[1087093440]: Maximum retries exceeded on call 6fa6b5c02082fcd9329ce282282a3dfa@10.10.10.1 for seqno 0 (Non-critical Re
sponse)
Comments:By: Mark Spencer (markster) 2004-08-30 09:06:01

You should enable sip history in sip.conf and then do "sip show history <callid>" so we can see what's going on, but it appears that the phone is trying to make an invalid transfer.
By: Mark Spencer (markster) 2004-08-31 00:18:35

still here?
By: bfranks (bfranks) 2004-08-31 00:24:47

Hi Mark,

Unfortuantely, I had to roll back to the last version of CVS because today was hell at the office.  Business was impacted by this problem.  I will try to lab it up this weekend when I can fully test and document the problem.

I also know from today that when doing a sip show channels, I saw like 20 or so UNKN channels, with the last message being REFER.

Not sure if thats any assistance, but sorry I can not offer you any quicker feedback than this.  Unfortuantely, the people that I run this for (pro bono) don't appreciate it when (they're non technical) the phone system doesnt work as expected.

- Brent
By: Mark Spencer (markster) 2004-08-31 00:40:30

Let me know as soon as you can, as we are approaching a 1.0 release of Asterisk.
By: bfranks (bfranks) 2004-08-31 17:29:37

Possibly, I can't confirm until this weekend that the channels that were having problems were with phones that are running SIP software version 1.1.0 from polycom.  I thought everything in mysetup was running at least 1.2.

By the end of the day I had 50 or so calls that looked like this:

10.10.60.16 (None) 6fa6b5c0208 00101/00002 UNKN
10.10.60.9 (None) 034cb51b7d2 00101/00004 UNKN
10.10.60.16 (None) 7daa434f2d4 00101/00002 UNKN
10.10.60.9 (None) 419bd02f2eb 00101/00004 UNKN

All calls had either .9 or .16.  After prelim investigation, it looks like those two phones have 1.1.0 running.  Will confirm this weekend.
By: Mark Spencer (markster) 2004-09-03 21:05:26

How did the testing go?
By: bfranks (bfranks) 2004-09-04 14:28:36

Going into the office sunday night...

- B
By: bfranks (bfranks) 2004-09-05 23:54:00

Did testing tonight and could not reproduce the problem at low call volume.  I will leave it running for Tuesday.  Since it is a holiday, call volume will also be low tom.

Will keep you updated.

- B
By: Mark Spencer (markster) 2004-09-07 10:41:54

How did it go today?
By: bfranks (bfranks) 2004-09-07 10:52:15

So far so good, I haven't heard any complaints.

I did a sip show channels, and there aren't any left calls showing up...

Only thing in the logs today is 3: Maximum retries exceeded on call 34b9b3487c
199e50359afd9706824709@10.10.10.1 for seqno 102 (Non-critical Request)

entries..

I should also point out that the phones were all upgraded to latest firmware, so maybe that helped resolve the situation.

- B
By: bfranks (bfranks) 2004-09-07 15:33:26

Mark,

Everything is still running fine.  You can close this bug.

- B