cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
9762
Views
0
Helpful
13
Replies

"all circuits are busy" - Internal Sever Error

mcastrigno
Level 1
Level 1

I am trying to figure out a recent problem. I have one SIP trunk.

If I am on the phone and a call comes in I get a the message "all circuits are busy" (not from my uc500)

Any and all responses appreciated.

Here is the message detail:

UC520#debug ccsip messages
SIP Call messages tracing is enabled
UC520#term mon
UC520#
Dec 15 22:05:22.658: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:+12083506322@24.119.219.2:5060;transport=udp SIP/2.0
Record-Route: <sip:216.82.224.202;lr;ftag=VPSF506071629460>
Record-Route: <sip:67.231.8.93;lr=on;ftag=VPSF506071629460>
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bK68c.70708603.0
Via: SIP/2.0/UDP 67.231.8.93;branch=z9hG4bK68c.9def0604.1
Via: SIP/2.0/UDP 4.68.250.148:5060;branch=z9hG4bK506071629460-1256706239266
From: "Unavailable"  <sip:+12088594276@4.68.250.148>;tag=VPSF506071629460
To: <sip:+12083506322@67.231.8.93:5060>
Call-ID: SEAMGC0320091215220427040455@209.244.62.70
CSeq: 1 INVITE
Contact: <sip:+12088594276@4.68.250.148:5060;transport=udp>
Max-Forwards: 67
Content-Type: application/sdp
Content-Length: 171
Remote-Party-ID: "Unavailable"    <sip:+12088594276@4.68.250.148>;party=calling;
screen=yes;privacy=off

v=0
o=- 1260914667 1260914668 IN IP4 63.215.28.37
s=-
c=IN IP4 63.215.28.37
t=0 0
m=audio 60658 RTP/AVP 0 18 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Dec 15 22:05:22.666: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 580 Precondition Failed
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bK68c.70708603.0,SIP/2.0/UDP 67.231.
8.93;branch=z9hG4bK68c.9def0604.1,SIP/2.0/UDP 4.68.250.148:5060;branch=z9hG4bK50
6071629460-1256706239266
From: "Unavailable"  <sip:+12088594276@4.68.250.148>;tag=VPSF506071629460
To: <sip:+12083506322@67.231.8.93:5060>;tag=68A8C05C-1E27
Date: Tue, 15 Dec 2009 22:05:22 GMT
Call-ID: SEAMGC0320091215220427040455@209.244.62.70
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 INVITE
Allow-Events: telephone-event
Content-Length: 0


Dec 15 22:05:22.762: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 580 Precondition Failed
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bK68c.70708603.0,SIP/2.0/UDP 67.231.
8.93;branch=z9hG4bK68c.9def0604.1,SIP/2.0/UDP 4.68.250.148:5060;branch=z9hG4bK50
6071629460-1256706239266
From: "Unavailable"  <sip:+12088594276@4.68.250.148>;tag=VPSF506071629460
To: <sip:+12083506322@67.231.8.93:5060>;tag=68A8C05C-1E27
Call-ID: SEAMGC0320091215220427040455@209.244.62.70
CSeq: 1 INVITE
Content-Length: 0

Dec 15 22:05:22.794: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:+12083506322@24.119.219.2:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bK68c.70708603.0
From: "Unavailable"  <sip:+12088594276@4.68.250.148>;tag=VPSF506071629460
Call-ID: SEAMGC0320091215220427040455@209.244.62.70
To: <sip:+12083506322@67.231.8.93:5060>;tag=68A8C05C-1E27
CSeq: 1 ACK
Max-Forwards: 70
User-Agent: Bandwidth.com TRM (bw7.gold.13)
Content-Length: 0

Dec 15 22:05:22.818: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:+12083506322@24.119.219.2:5060;transport=udp SIP/2.0
Record-Route: <sip:216.82.225.202;lr;ftag=VPSF506071629460>
Record-Route: <sip:67.231.8.93;lr=on;ftag=VPSF506071629460>
Via: SIP/2.0/UDP 216.82.225.202;branch=z9hG4bK68c.4deb5902.0
Via: SIP/2.0/UDP 67.231.8.93;branch=z9hG4bK68c.9def0604.2
Via: SIP/2.0/UDP 4.68.250.148:5060;branch=z9hG4bK506071629460-1256706239266
From: "BOISE        ID"  <sip:+12088594276@4.68.250.148>;tag=VPSF506071629460
To: <sip:+12083506322@67.231.8.93:5060>
Call-ID: SEAMGC0320091215220427040455@209.244.62.70
CSeq: 1 INVITE
Contact: <sip:+12088594276@4.68.250.148:5060;transport=udp>
Max-Forwards: 67
Content-Type: application/sdp
Content-Length: 171

v=0
o=- 1260914667 1260914668 IN IP4 63.215.28.37
s=-
c=IN IP4 63.215.28.37
t=0 0
m=audio 60658 RTP/AVP 0 18 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Dec 15 22:05:22.826: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 580 Precondition Failed
Via: SIP/2.0/UDP 216.82.225.202;branch=z9hG4bK68c.4deb5902.0,SIP/2.0/UDP 67.231.
8.93;branch=z9hG4bK68c.9def0604.2,SIP/2.0/UDP 4.68.250.148:5060;branch=z9hG4bK50
6071629460-1256706239266
From: "BOISE        ID"  <sip:+12088594276@4.68.250.148>;tag=VPSF506071629460
To: <sip:+12083506322@67.231.8.93:5060>;tag=68A8C0FC-1661
Date: Tue, 15 Dec 2009 22:05:22 GMT
Call-ID: SEAMGC0320091215220427040455@209.244.62.70
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 INVITE
Allow-Events: telephone-event
Content-Length: 0


Dec 15 22:05:22.826: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:+12083506322@24.119.219.2:5060;transport=udp SIP/2.0
Record-Route: <sip:216.82.225.202;lr;ftag=VPSF506071629460>
Record-Route: <sip:67.231.8.93;lr=on;ftag=VPSF506071629460>
Via: SIP/2.0/UDP 216.82.225.202;branch=z9hG4bK68c.5deb5902.0
Via: SIP/2.0/UDP 67.231.8.93;branch=z9hG4bK68c.9def0604.3
Via: SIP/2.0/UDP 4.68.250.148:5060;branch=z9hG4bK506071629460-1256706239266
From: "BOISE        ID"  <sip:+12088594276@4.68.250.148>;tag=VPSF506071629460
To: <sip:+12083506322@67.231.8.93:5060>
Call-ID: SEAMGC0320091215220427040455@209.244.62.70
CSeq: 1 INVITE
Contact: <sip:+12088594276@4.68.250.148:5060;transport=udp>
Max-Forwards: 67
Content-Type: application/sdp
Content-Length: 171

v=0
o=- 1260914667 1260914668 IN IP4 63.215.28.37
s=-
c=IN IP4 63.215.28.37
t=0 0
m=audio 60658 RTP/AVP 0 18 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Dec 15 22:05:22.830: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 482 Loop Detected
Via: SIP/2.0/UDP 216.82.225.202;branch=z9hG4bK68c.5deb5902.0,SIP/2.0/UDP 67.231.
8.93;branch=z9hG4bK68c.9def0604.3,SIP/2.0/UDP 4.68.250.148:5060;branch=z9hG4bK50
6071629460-1256706239266
From: "BOISE        ID"  <sip:+12088594276@4.68.250.148>;tag=VPSF506071629460
To: <sip:+12083506322@67.231.8.93:5060>;tag=68A8C0FC-1661
Call-ID: SEAMGC0320091215220427040455@209.244.62.70
CSeq: 1 INVITE
Reason: Q.850;cause=127
Content-Length: 0

Dec 15 22:05:22.886: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:+12083506322@24.119.219.2:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 216.82.224.202;branch=z9hG4bK68c.70708603.0
From: "Unavailable"  <sip:+12088594276@4.68.250.148>;tag=VPSF506071629460
Call-ID: SEAMGC0320091215220427040455@209.244.62.70
To: <sip:+12083506322@67.231.8.93:5060>;tag=68A8C05C-1E27
CSeq: 1 ACK
Max-Forwards: 70
User-Agent: Bandwidth.com TRM (bw7.gold.13)
Content-Length: 0

Dec 15 22:05:22.918: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:+12083506322@24.119.219.2:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 216.82.225.202;branch=z9hG4bK68c.4deb5902.0
From: "BOISE        ID"  <sip:+12088594276@4.68.250.148>;tag=VPSF506071629460
Call-ID: SEAMGC0320091215220427040455@209.244.62.70
To: <sip:+12083506322@67.231.8.93:5060>;tag=68A8C0FC-1661
CSeq: 1 ACK
Max-Forwards: 70
User-Agent: Bandwidth.com TRM (gold.13)
Content-Length: 0

Dec 15 22:05:22.942: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:+12083506322@24.119.219.2:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 216.82.225.202;branch=z9hG4bK68c.5deb5902.0
From: "BOISE        ID"  <sip:+12088594276@4.68.250.148>;tag=VPSF506071629460
Call-ID: SEAMGC0320091215220427040455@209.244.62.70
To: <sip:+12083506322@67.231.8.93:5060>;tag=68A8C0FC-1661
CSeq: 1 ACK
Max-Forwards: 70
User-Agent: Bandwidth.com TRM (gold.13)
Content-Length: 0

1 Accepted Solution