Kurt Harnish Posted June 28, 2011 Report Share Posted June 28, 2011 It is a PRI through Windstream. Incoming calls are working correctly but outgoing does not. Here is a debug from the Sangoma card. Codeset: 6 DISPLAY 28 0b 4b 75 72 74 20 4c 61 6e 64 69 73 2011-06-28 08:46:26:159 -0400 [5189:5341] INFO - netborder.pstn.sangoma.isdn.message.b1(B1 - A101_digital)di1(B1I1)-c23 : call-id=1309265186-61316-235745791-231 RECEIVING ISDN MESSAGE in LAPD PRIMITIVE DL_DA_IN via span 0 RELEASE_COMPLETE Crv: 0x8001 Codeset: 0 CAUSE 08 04 82 ac 18 17 Len: 4 82: 1... .... : Extension indicator : Last octet .00. .... : Coding Standard : ITU-T standardized coding .... 0010 : Location : Public network serving the local user (LN) Cause: Requested circuit/channel not available 2011-06-28 08:46:26:161 -0400 [5189:5254] INFO - netborder.pstn.sangoma.isdn.channel : call-id=1309265186-61316-235745791-231 [CALLING] No channel is available or the channel required as "exclusive" in previously sent SETUP message was refused. Event : connid=x3, chan=x17 : N_STATUS_INDICATION - Incoming call NO CHANNEL available! 2011-06-28 08:46:26:161 -0400 [5189:5254] INFO - netborder.pstn.sangoma.isdn.channel : call-id=1309265186-61316-235745791-231 Make call operation failed because of reception of a DISCONNECT with ISDN cause=0x2c. No ressource are available for the outbound call. 2011-06-28 08:46:26:162 -0400 [5189:5254] INFO - netborder.pstn.sangoma.isdn.channel : call-id=1309265186-61316-235745791-231 [CALLING] MakeCall operation failed. Cause=NO_RESOURCE_CONN_FAILURE 2011-06-28 08:46:26:162 -0400 [5189:5254] INFO - netborder.pstn.BidirStateMachine.b1(B1 - A101_digital)di1(B1I1)-c23 : call-id=1309265186-61316-235745791-231 Failed to make outbound pstn call : All trunks are busy 2011-06-28 08:46:26:163 -0400 [5189:5246] INFO - netborder.gw.CallLegWrapper : call-id=1309265186-61316-235745791-231 INLEG inviteRejected : NO_RESOURCE_CONN_FAILURE 2011-06-28 08:46:26:164 -0400 [5189:5246] INFO - netborder.cdr : call-id=1309265186-61316-235745791-231 Call ended Tue Jun 28 08:46:26 2011 2011-06-28 08:46:26:164 -0400 [5189:5253] DEBUG - netborder.voip.StateMachine.In : call-id=1309265186-61316-235745791-231 VoipStateMachine processing event eAPI_INVITE_REJECTED 2011-06-28 08:46:26:166 -0400 [5189:5253] INFO - netborder.sip.message : call-id=1309265186-61316-235745791-231 SENDING SIP MESSAGE (RESPONSE) via UDP to 127.0.0.1:5060 : SIP/2.0 503 Service Unavailable Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-f1f3ea6b2430264a0fc9501b7c9f1699;rport=5060 From: "user" <sip:888@snomone.pbx.com;user=phone>;tag=868794664 To: <sip:7177330793@127.0.0.1:7066;user=phone>;tag=ds-7f6af5df-3953f164 Call-ID: 16a78289@pbx CSeq: 29047 INVITE Content-Length: 0 Server: Netborder Express Gateway/4.1.1 CPD-Result: ??? Contact: <sip:127.0.0.1:7066;transport=udp> Thank you, Kurt Quote Link to comment Share on other sites More sharing options...
gotvoip Posted June 28, 2011 Report Share Posted June 28, 2011 What does the channel status show? Are the B channels idle or in service? You can chat directly with Sangoma support at http://wiki.sangoma.com/SangomaTechSupport for live help. Sounds like there is some initialization/config issue. Strange how it works one way but not the other. Quote Link to comment Share on other sites More sharing options...
Kurt Harnish Posted June 28, 2011 Author Report Share Posted June 28, 2011 It is showing that all of the channels are idle and ready. Quote Link to comment Share on other sites More sharing options...
Vodia support Posted June 29, 2011 Report Share Posted June 29, 2011 Are there any errors on the System status screen? Quote Link to comment Share on other sites More sharing options...
Kurt Harnish Posted June 29, 2011 Author Report Share Posted June 29, 2011 This error was on this morning Alarm [system.overload.cpu] : ALARM_ON Quote Link to comment Share on other sites More sharing options...
Vodia support Posted June 29, 2011 Report Share Posted June 29, 2011 I would proceed to the following URL http://wiki.sangoma.com/SangomaTechSupport Sangoma support is usually on the IRC chat live and I would also open ticket with them as well. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.