Can someone help me 8

[pjj06]

I can recieve calls but I cant make them with our outside line (PRI),

CMReleaseComp
Line: type=Q931Line 1 Call: lid=1 id=2 in=1
Cause=34, No cct/chan available

does this error mean anything to you guy's?

Paul

 

[MrIPO]

Looking at it I would say you have issues with your ISDN lines when you are trying to get a channel, can you please do a L3ISDN Events / L3 ISDN Send and receive trace and post for when the issue happens. You may be getting a code back from the carrier, but I cannot see it on a CM Message. We need to look @ a higher level.

http://www.iporesource.com

"Launching late 2006

 

[pjj06]

Hi MrIPO,

Thankyou for your help, I've added L3, here is the result, will this help you?


265636mS ISDNL3Evt: v=1 stacknum=1 State, new=Initiated, old=NullState id=1003
265657mS ISDNL3Evt: v=1 stacknum=1 State, new=NullState, old=Initiated id=1003
265663mS CMLineRx: v=1
CMReleaseComp
Line: type=Q931Line 1 Call: lid=0 id=1003 in=0
Cause=34, No cct/chan available


Paul

 

[franke]

What protocol are you set for (i.e.: NI2, Local Telco, AT&T, etc.), are your short codes for outgoing calls set for the correct line group (and in LCR, if you're using it)?

franke

 

[pjj06]

Hi Franke, I'm not sure if I've understood the question, I'm using the following short code 0N N 0
Whereas 0 is the line group, but it seems to be disconected. But I'm also using the line group 0 for the incomeing calls and that works!

What I don't understand is why did it work for almost 3 months without any problems, but since the russian telephone company re-connected the line after they had accidently disconetced it, it doesn't work any more.


68673mS CMTARGET: SELECT:37 0 0 TGHG=00000000 TGUSER=fef1b068 INCL=00000008 EXCL=00000008
68674mS CMTARGET: ADD USER:37 Codest Fax(3478, state=UNKNOWN) (depth=1 B=13) cw=0
68674mS CMTARGET: SELECT:37 NO TARGETS, TRY VOICEMAIL
68674mS CMTARGET: SELECT:37 BUSY
68674mS PRN: CALL: 1.29.1 Deleted leaving 0 CMCall objects
68674mS CMMap: a=2.2 b=0.0 R0
68674mS CMCallEvt: v=29 State, new=Idle old=Connected,0,0,Astate
68674mS CMCallEvt: v=29 State, new=Idle old=ReDialling,0,0,BState
68675mS CALL:2006/07/0718:13,00:00:05,000,00390516024774,I,3478,5101977,,,,0,,""
68675mS CMLineTx: v=1
CMReleaseComp
Line: type=Q931Line 1 Call: lid=1 id=29 in=1
Cause=34, No cct/chan available
68675mS CD: CALL: 1.29.1 Deleted
68678mS ISDNL3Evt: v=1 stacknum=1 State, new=DiscReq, old=Active id=-1
68678mS ISDNL3Tx: v=1 peb=1
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=04D7(Local)
Message Type = Disconnect
InformationElement = CAUSE
0000 08 02 80 a2 ....
68698mS ISDNL3Rx: v=1 peb=1
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=04D7(Remote)
Message Type = Release
68699mS ISDNL3Tx: v=1 peb=1
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=04D7(Local)
Message Type = ReleaseComplete
68699mS ISDNL3Evt: v=1 stacknum=1 State, new=NullState, old=DiscReq id=-1
69662mS CMExtnEvt: v=1013 State, new=Idle old=PortRecoverDelay,0,0,
69662mS CMExtnTx: v=, p1=1013
CMReleaseComp
Line: type=RAS 1 Call: lid=0 id=1013 in=0
BChan: slot=6 chan=20
Cause=126, Transfer(IPO)


Thanks you very much for your help
Paul

 

[jconrad0305]

is the pri set to out of service. i have had it happen were it will work for incoming calls but ipo will bar outgoing calls

 

[pjj06]

Hi Jconrad0305,

Can the PRI be set to OUT OF SERVICE? If so, by whom, the Russian Telephone Company or by me by mistake on our 406 IP OFFICE?

I honestly hope that it is the Russian Telephone company who is blocking my out going calls, but I don't know how to explain it to them (

Please answere and Thank you

Paul

 

[IPGuru]

I dont know much on the Russian Telephone company , but if I was gettig these symptoms in the UK I would be screaming a BT to sort their end out
I would be supprised if this is not a telco issue

 

[pjj06]

IPGuru

Thanks for the confirmation, I'll try and talk or scream at the Russian Phone Company

Yet again thanks to all of you.

Paul

 

[intrigrant]

If you get a ISDN cause 34 then the CO did set up a PRI for you but they forgot? to assign channels.
So IPO will synchronize but it won't get any B-channel from the CO.

 

[PrivateBuild]

The "a2" Disconnect that is in your trace means there is "No circuit/channel available" and the "ISDNL3Tx" means that the IPO has sent this message. This is what Intrigrant has pointed out. You can go to the carrier with this part of the trace and ask them to investigate.

68678mS ISDNL3Tx: v=1 peb=1
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=04D7(Local)
Message Type = Disconnect
InformationElement = CAUSE
0000 08 02 80 a2

 

[pjj06]

Intrigrant and PrivateBuild,

Thank you very much for the explanation.

Paul

 

[intrigrant]

No worries, could you solve the problem?

 

[aramsay]

We get a similar sort of problem here in the UK with Telewest.

If we reboot the IPO more than 3 times within an hour, Telewest take the PRI out of service (automatically); it requires a call to their NOC, followed by a call to my TAM, followed by lots of banging things and shouting to get it brought back into service.

Alan

 

[pjj06]

Still not working, they say (Russian Telephone Company) that it should work, but I still get the (Cause=34, No cct/chan available). My boss thinks that it might be my fault and not because they forgot to pay the invoice )

My Log

1880924mS CD: CALL: 43.1.2 BState=Idle Cut=1 Music=0.0 Aend="Line 43" (250.10001) Bend="Line 1" [Line 1] (0.0) CalledNum=9162091 () CallingNum=4774 () Internal=0 Time=3 AState=Dialling
1880925mS CMLineTx: v=1
CMSetup
Line: type=Q931Line 1 Call: lid=0 id=1591 in=0
Called[9162091] Type=Unknown (0) Calling[4774] Type=Unknown (0)
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
IE CMIETxChannelAudio (1) comptype=G729A8K (6) pktsize=20 ipaddr=10.0.253.250 port=49326
Display [Jenner Jones P]
Cause=16, Normal call clearing
Locale: ita
1880930mS ISDNL3Evt: v=1 stacknum=1 State, new=Initiated, old=NullState id=1591
1880930mS ISDNL3Tx: v=1 peb=1
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0010(Remote)
Message Type = Setup
InformationElement = BearerCapability
0000 04 03 80 90 a3 .....
InformationElement = CallingPartyNumber
0000 6c 05 80 34 37 37 34 l..4774
InformationElement = CalledPartyNumber
0000 70 08 80 39 31 36 32 30 39 31 p..9162091
1880973mS ISDNL3Rx: v=1 peb=1
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0010(Local)
Message Type = ReleaseComplete
InformationElement = CAUSE
0000 08 03 82 a2 ff .....
1880973mS ISDNL3Evt: v=1 stacknum=1 State, new=NullState, old=Initiated id=1591
1880979mS CMLineRx: v=1
CMReleaseComp
Line: type=Q931Line 1 Call: lid=0 id=1591 in=0
Cause=34, No cct/chan available
1880979mS CMCallEvt: v=1 State, new=Disconnecting old=Idle,0,0,BState
1880979mS CD: CALL: 43.1.2 BState=Disconnecting Cut=1 Music=0.0 Aend="Line 43" (250.10001) Bend="Line 1" [Line 1] (0.0) CalledNum=9162091 () CallingNum=4774 () Internal=0 Time=58 AState=Dialling
1880979mS PRN: CALL: 43.1.2 Deleted leaving 0 CMCall objects
1880979mS CMCallEvt: v=1 State, new=Idle old=Dialling,0,0,Astate
1880980mS CMCallEvt: v=1 State, new=Idle old=Disconnecting,0,0,BState
1880980mS CALL:2006/07/1314:05,00:00:00,000,4774,I,9162091,8349162091,,,,0,,""
1880980mS CMLineTx: v=43
CMReleaseComp
Line: type=IPLine 43 Call: lid=0 id=1 in=2
Cause=34, No cct/chan available
1880981mS CD: CALL: 43.1.2 Deleted
1880982mS H323Evt: v=0 stacknum=43 State, new=NullState, old=Present id=1


Paul

 

[NewNic]

your gona have to get someone in the co to actualy work with you real time (what a concept)With your logs and a true CO tech you will be able to sort it out.

These cause codes are not something that Avaya has just made up, they are industry standard for ISDN. The CO tech will be able to see the same thing, Your just gona have to get to the point of working real time with one

 

[NuggiFirst]

Also:
If you have an ISDN30 tested at hand, then confirm the problem with the tester.
Then the operator should take the matter a bit more serious.

 

[IPGuru]

You are sending the call to line
the clear cause isd being recieved from the network
this is a network issue
insist that you line provider send an engineer to test from site.
(I would bet that the line miraculously starts working just before he arives!)