Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

TRUNK GROUP 5 cause code 44

Status
Not open for further replies.

sixteamparlay

IS-IT--Management
Aug 1, 2008
46
US
I attached the log from our Sangoma IP Gateway that sends calls to Avaya Trunk group 5

We dial 1200 from the IP pbx and it is routed to Avaya, Avaya immediately returns "CAUSE 08 02 81 ac" which is cause code 44

The avaya is setup to accept incoming digits of length 4 to 1200 to forward to be replaced by 7556 on the Avaya side but Avaya never forwards the call. Is there a way to trace the call on Avaya Definity?

The significant part of the log is here:

SETUP
Crv: 0x0001
Codeset: 0
BEARER_CAPABILITY 04 03 80 90 a2
CHANNEL_IDENTIFICATION 18 03 a9 83 97
CALLED_PARTY_NUMBER 70 05 80 31 32 30 30
2009-02-12 10:54:15:136 [3580] INFO - netborder.pstn.sangoma.isdn.message.s0-XYZspan0-c23 : RECEIVING ISDN MESSAGE in LAPD PRIMITIVE DL_DA_IN via span 0
RELEASE_COMPLETE
Crv: 0x8001
Codeset: 0
CAUSE 08 02 81 ac



------------

2009-02-12 10:54:15:103 [4068] INFO - netborder.infra.CallLogger.Appender : Call start : 02/12/09 10:54:15
2009-02-12 10:54:15:103 [2644] INFO - netborder.cdr : Call started 02/12/09 10:54:15
2009-02-12 10:54:15:103 [4068] INFO - netborder.sip.message : RECEIVED SIP MESSAGE (REQUEST) via UDP from 127.0.0.1:5060 :
INVITE sip:1200@127.0.0.1:5066;user=phone SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;rport=5060;branch=z9hG4bK-c982bd18b25208fb00a7f52cb9187f59
From: "Wireless One" <sip:7756@pbx.gntrad.local>;tag=24277
To: <sip:1200@127.0.0.1:5066;user=phone>;tag=ds-323b-3f845f6
Call-ID: e222f1e2@pbx
CSeq: 20262 INVITE
Max-Forwards: 70
Contact: <sip:7756@127.0.0.1:5060;transport=udp>
Supported: 100rel
Supported: replaces
Supported: norefersub
Allow-Events: refer
Allow: INVITE
Allow: ACK
Allow: CANCEL
Allow: BYE
Allow: REFER
Allow: PRACK
Allow: INFO
Allow: UPDATE
Accept: application/sdp
User-Agent: pbxnsip-PBX/3.1.1.3110
P-Asserted-Identity: "Wireless One" <sip:7756@pbx.gntrad.local>
Content-Type: application/sdp
Content-Length: 331

v=0
o=- 49633 49633 IN IP4 127.0.0.1
s=-
c=IN IP4 127.0.0.1
t=0 0
m=audio 62012 RTP/AVP 0 8 9 18 2 3 101
a=rtpmap:0 pcmu/8000
a=rtpmap:8 pcma/8000
a=rtpmap:9 g722/8000
a=rtpmap:18 g729/8000
a=fmtp:18 annexb=no
a=rtpmap:2 g726-32/8000
a=rtpmap:3 gsm/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=sendrecv


2009-02-12 10:54:15:103 [2644] INFO - netborder.cdr : SIP IN
2009-02-12 10:54:15:104 [4068] INFO - netborder.sip.message : SENDING SIP MESSAGE (RESPONSE) via UDP to 127.0.0.1:5060 :
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-c982bd18b25208fb00a7f52cb9187f59;rport=5060
From: "Wireless One" <sip:7756@pbx.gntrad.local>;tag=24277
To: <sip:1200@127.0.0.1:5066;user=phone>;tag=ds-323b-3f845f6
Call-ID: e222f1e2@pbx
CSeq: 20262 INVITE
Content-Length: 0
Server: Netborder Express Gateway/1.6.3
Contact: <sip:NetborderExpressGateway@127.0.0.1:5066;transport=udp>



2009-02-12 10:54:15:107 [4068] INFO - netborder.cdr.voip : IN From Header= sip:7756@pbx.gntrad.local
2009-02-12 10:54:15:107 [4068] INFO - netborder.cdr.voip : IN To Header= sip:1200@127.0.0.1:5066;user=phone
2009-02-12 10:54:15:107 [1680] INFO - netborder.media.jrtp.endpoint : ept-id=0 RTCP is enabled
2009-02-12 10:54:15:114 [3900] INFO - netborder.gw.routing.GWRoutingSession : ROUTING RESULT:
1 RULE(S) FIRED
Trying:
- q-value=0.001 Rule name=default_pstn_out RoutedLegInfo=sip.in.requestUri=sip:1200@127.0.0.1:5066;user=phone
sip.in.requestUri.canonical=sip:1200@127.0.0.1:5066
sip.in.from.uri=sip:7756@pbx.gntrad.local
sip.in.from.uri.canonical=sip:7756@172.16.199.199:5060
sip.in.from.displayName="Wireless One"
sip.in.to.uri=sip:1200@127.0.0.1:5066;user=phone
sip.in.to.uri.canonical=sip:1200@127.0.0.1:5066
sip.in.to.displayName=
sip.in.header.Via=SIP/2.0/UDP 127.0.0.1:5060;rport=5060;branch=z9hG4bK-c982bd18b25208fb00a7f52cb9187f59
sip.in.header.CSeq=20262 INVITE
sip.in.header.Call-ID=e222f1e2@pbx
sip.in.header.Content-Length=331
sip.in.header.Contact=<sip:7756@127.0.0.1:5060;transport=udp>
sip.in.header.P-Asserted-Identity="Wireless One" <sip:7756@pbx.gntrad.local>
media.rtp.stream0=sendrecv
transfer=false
pstn.out.phoneNumber=1200
pstn.out.deviceGroup=default
pstn.out.cpa.enable=false
2009-02-12 10:54:15:115 [2644] INFO - paraxip.cdr : PSTN OUT
2009-02-12 10:54:15:115 [3548] INFO - paraxip.pstn.BidirStateMachine.s0-XYZspan0-c23 : Using channelName "s0-XYZspan0-c23" for pstn out
2009-02-12 10:54:15:115 [3548] INFO - paraxip.pstn.BidirStateMachine.s0-XYZspan0-c23 : pstn.out.phoneNumber = 1200
2009-02-12 10:54:15:115 [3548] INFO - netborder.cdr.pstn : Outgoing Leg DNIS = 1200
2009-02-12 10:54:15:116 [3548] INFO - netborder.cdr.pstn : Outgoing Leg ANI = unknown-ani
2009-02-12 10:54:15:116 [2300] INFO - netborder.pstn.sangoma.isdn.message.s0-XYZspan0-c23 : TRANSMITTING ISDN MESSAGE via span 0
SETUP
Crv: 0x0001
Codeset: 0
BEARER_CAPABILITY 04 03 80 90 a2
CHANNEL_IDENTIFICATION 18 03 a9 83 97
CALLED_PARTY_NUMBER 70 05 80 31 32 30 30
2009-02-12 10:54:15:136 [3580] INFO - netborder.pstn.sangoma.isdn.message.s0-XYZspan0-c23 : RECEIVING ISDN MESSAGE in LAPD PRIMITIVE DL_DA_IN via span 0
RELEASE_COMPLETE
Crv: 0x8001
Codeset: 0
CAUSE 08 02 81 ac
2009-02-12 10:54:15:136 [3548] INFO - netborder.pstn.sangoma.isdn.channel.s0-XYZspan0-c23 : [CALLING] MakeCall operation failed. Cause=NO_RESOURCE_CONN_FAILURE
2009-02-12 10:54:15:136 [3548] INFO - paraxip.pstn.BidirStateMachine.s0-XYZspan0-c23 : Failed to make outbound pstn call : All trunks are busy
2009-02-12 10:54:15:136 [2644] INFO - netborder.gw.CallLegWrapper : INLEG inviteRejected : NO_RESOURCE_CONN_FAILURE
2009-02-12 10:54:15:137 [2644] INFO - netborder.cdr : Call ended 02/12/09 10:54:15
2009-02-12 10:54:15:137 [4068] INFO - netborder.sip.message : SENDING SIP MESSAGE (RESPONSE) via UDP to 127.0.0.1:5060 :
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-c982bd18b25208fb00a7f52cb9187f59;rport=5060
From: "Wireless One" <sip:7756@pbx.gntrad.local>;tag=24277
To: <sip:1200@127.0.0.1:5066;user=phone>;tag=ds-323b-3f845f6
Call-ID: e222f1e2@pbx
CSeq: 20262 INVITE
Content-Length: 0
Server: Netborder Express Gateway/1.6.3
CPD-Result: ???
Contact: <sip:172.16.199.199:5066;transport=udp>



2009-02-12 10:54:15:137 [4068] INFO - netborder.voip.StateMachine.In : sip call ended 02/12/09 10:54:15
2009-02-12 10:54:15:138 [1680] INFO - netborder.media.jrtp.endpoint : ept-id=0 RTP Stats
Sent 0 packet(s)
Received 0 packet(s)

2009-02-12 10:54:15:144 [512] INFO - netborder.sip.message : RECEIVED SIP MESSAGE (REQUEST) via UDP from 127.0.0.1:5060 :
ACK sip:1200@127.0.0.1:5066;user=phone SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;rport=5060;branch=z9hG4bK-c982bd18b25208fb00a7f52cb9187f59
From: "Wireless One" <sip:7756@pbx.gntrad.local>;tag=24277
To: <sip:1200@127.0.0.1:5066;user=phone>;tag=ds-323b-3f845f6
Call-ID: e222f1e2@pbx
CSeq: 20262 ACK
Max-Forwards: 70
Contact: <sip:7756@127.0.0.1:5060;transport=udp>
P-Asserted-Identity: "Wireless One" <sip:7756@pbx.gntrad.local>
Content-Length: 0



2009-02-12 10:57:15:091 [3860] INFO - netborder.infra.CallLogger.Appender : Call end : 02/12/09 10:57:15
 
Command: list trace TAC (tac for trunk-group 5)

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
 
This is what it means:

Cause No. 44 - requested circuit/channel not available.
This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other side of the interface.


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Implement IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Why would the Avaya say the requested circuit is not available? Is there a way to list the trunk and channels 1-23 status? The far end (IP PBX) shows the T1 as up and all 23 channels as IDLE.
 
Command: status trunk 5

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
 
Command: list trace TAC (tac for trunk-group 5)

how do i stop this command once it is started?
 
Hit the cancel button.

Susan
"An education isn't how much you have committed to memory, or even how much you know. It's being able to differentiate between what you do know and what you don't."
- Anatole France
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top