[asterisk-bugs] [Asterisk 0018359]: Problem parked in asterisk

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Nov 24 19:52:40 CST 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18359 
====================================================================== 
Reported By:                alexfaiotto
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18359
Category:                   Channels/chan_sip/General
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.0 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.8 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-11-23 13:36 CST
Last Modified:              2010-11-24 19:52 CST
====================================================================== 
Summary:                    Problem parked in asterisk
Description: 
Hi,

when I make a call parking is giving the error below, and not
unable to complete the parking lot.

I'm having problems with parked could help me


    -- Executing [700 at Administrativo:1] Dial("SIP/202-00000003",
"SIP/700,50,tTwW") in new stack
  == Using UDPTL CoS mark 5
  == Using SIP RTP CoS mark 5
[Nov 23 17:26:47] WARNING[19228]: acl.c:698 ast_ouraddrfor: Cannot
connect
[Nov 23 17:26:47] WARNING[19228]: chan_sip.c:3112 __sip_xmit: sip_xmit of
0xb7aedc80 (len 846) to 0.0.2.188:50
60 returned -1: Invalid argument
    -- Called 700
[Nov 23 17:26:48] WARNING[19167]: chan_sip.c:3112 __sip_xmit: sip_xmit of
0xb7aedc80 (len 846) to 0.0.2.188:50
60 returned -1: Invalid argument
[Nov 23 17:26:49] WARNING[19167]: chan_sip.c:3112 __sip_xmit: sip_xmit of
0xb7aedc80 (len 846) to 0.0.2.188:50
60 returned -1: Invalid argument
[Nov 23 17:26:51] WARNING[19167]: chan_sip.c:3112 __sip_xmit: sip_xmit of
0xb7aedc80 (len 846) to 0.0.2.188:50
60 returned -1: Invalid argument
[Nov 23 17:26:55] WARNING[19167]: chan_sip.c:3112 __sip_xmit: sip_xmit of
0xb7aedc80 (len 846) to 0.0.2.188:50
60 returned -1: Invalid argument
[Nov 23 17:27:03] WARNING[19167]: chan_sip.c:3112 __sip_xmit: sip_xmit of
0xb7aedc80 (len 846) to 0.0.2.188:50
60 returned -1: Invalid argument
[Nov 23 17:27:19] WARNING[19167]: chan_sip.c:3112 __sip_xmit: sip_xmit of
0xb7aedc80 (len 846) to 0.0.2.188:50
60 returned -1: Invalid argument
    -- SIP/700-00000004 is circuit-busy
  == Everyone is busy/congested at this time (1:0/1/0)
    -- Auto fallthrough, channel 'SIP/202-00000003' status is
'CONGESTION'
[Nov 23 17:27:19] WARNING[19167]: chan_sip.c:3383 retrans_pkt:
Retransmission timeout reached on transmission
5040e5024acadfed042ae4d22af8b487 at 127.0.0.1:5060 for seqno 102 (Critical
Request) -- See doc/sip-retransmit.txt
.
Packet timed out after 32000ms with no response
Centrix*CLI> exit
[root at Centrix ~]# asterisk -vvr
Verbosity is at least 3
[Nov 23 17:29:06] WARNING[19167]: chan_sip.c:3112 __sip_xmit: sip_xmit of
0xcc4fea8 (len 844) to 0.0.2.190:506
0 returned -1: Invalid argument
  == Spawn extension (Administrativo, 702, 1) exited non-zero on
'SIP/202-00000005'
[Nov 23 17:29:10] WARNING[19167]: chan_sip.c:3112 __sip_xmit: sip_xmit of
0xcc4fea8 (len 844) to 0.0.2.190:506
0 returned -1: Invalid argument
[Nov 23 17:29:18] WARNING[19167]: chan_sip.c:3112 __sip_xmit: sip_xmit of
0xcc4fea8 (len 844) to 0.0.2.190:506
0 returned -1: Invalid argument
====================================================================== 

---------------------------------------------------------------------- 
 (0129127) pabelanger (administrator) - 2010-11-24 19:52
 https://issues.asterisk.org/view.php?id=18359#c129127 
---------------------------------------------------------------------- 
We require a complete debug log to help triage the issue.

This document will provide instructions on how to collect debugging logs
from an Asterisk machine for the purpose of helping bug marshals
troubleshoot an issue:

https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-24 19:52 pabelanger     Note Added: 0129127                          
======================================================================




More information about the asterisk-bugs mailing list