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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP 500 V2 ISDN cant dial out or rx i/c calls - busy tone

Status
Not open for further replies.

bonus99

Technical User
Apr 9, 2003
55
GB
Have 2 x PRI - line 1 = 30 channels and line 5 = 8 channels.
I/C calls get busy, the only h/set on the system is unable to dial out.

Have checked it all and seems OK,am I missing something obvious here, its been a bad day and I am glad it is Friday!

Any help appreciated.

Thanks in advance

here is the trace


UNICODE-UTF8
eng
541271mS R2DSP: PRIU DSP 1: is alive
542436mS R2DSP: PRIU DSP 2: is alive
573862mS H323Evt: Recv: RegistrationRequest xxx.xx.x.xxx; Endpoints registered: 1; Endpoints in registration: 0

********** SysMonitor v8.0 (8) [connected to 10.10.2.5 (Chxxxxt IP500)] **********
579705mS PRN: Monitor Status IP 500 V2 6.0(8)
579705mS PRN: LAW=A PRI=2, BRI=0, ALOG=0, ADSL=0 VCOMP=32, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=1 VMAIL=1(VER=3 TYP=1) CALLS=0(TOT=0)
580133mS ISDNL3Rx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0035(Remote)
Message Type = Setup
InformationElement = Sending Complete
InformationElement = BearerCapability
0000 04 03 90 90 a3 .....
InformationElement = CHI
0000 18 03 a1 83 9f .....
InformationElement = CallingPartyNumber
0000 6c 0c 21 83 31 34 33 35 38 31 32 33 30 36 l.!.14xxxxxx06
InformationElement = CalledPartyNumber
0000 70 07 c9 34 39 37 32 34 30 p..4xxxx0
580134mS ISDNL3Evt: v=5 stacknum=5 State, new=NullState, old=NullState id=3
580134mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0035(Local)
Message Type = ReleaseComplete
InformationElement = CAUSE
0000 08 02 80 91 ....
 
Hi,thanks for your reply.

The channels are idle.
Yes the codes are OK.
 
Watching the call in SSA how does it progress? Does it attempt to dial then immediatly drop when it hits the line or does it hang on the line then timeout? Do you have a trend or similar to prove the NTE/lines and PRI cards? :)

ACSS (SME)
APSS (SME)

 
The trouble is...

I am not on site.

The busy tone/trace is instant.

I have just found out that this is connected to a call server acting as an exchange, this was previously working with errors due to a protocol problem that was fixed! I have been assured that the protocols are OK and it would make sense as L1/L2 are OK.
Both side get traces that seem OK but the call does not connect?
 
also...
there is no I/C short codes, there is an I/C call route for the DDI, set to an IP h/set (2000)
 
I would bet a months wages that the Call server is not emulating the lines correctly, there is not a great deal to be done IP Office side with regards to ISDN 30 and so not a lot you can get wrong :)

ACSS (SME)
APSS (SME)

 
sadly, I suspect you are right.

Will throw it back and let you know how i get on.

Thanks all for your help
 
Hello again.

Still have this problem. The client has double confirmed that their end is set up OK.

This is the dump from there network


[13:10:22:416] <0001136645> [189494:2]0FEFDF8D: TX:02,01,06,06,08,02,00,39,05,A1,04,03,80,90,A3,18,03,A1,83,9F,6C,0C,21,83,32,30,37,33,30,36,37,36,34,36,70,07,C9,34,39,37,32,34,30,
Transmit
Port - [189494:2]
Time - [13:10:22:416]
SAPI - 0
C/R - 1
TEI - 0
I-Format
Transmit Sequence Number - 3
Receive Sequence Number - 3
P/F bit - 0
Protocol Discriminator - 8
Call Ref Length - 2
Call Ref Flag - 0
Call Reference - 39
message type - SETUP
*sending complete - a1
*bearer - 4 3 80 90 a3
coding standard - CCITT standard
information transfer capability - speech
transfer mode - circuit mode
transfer rate - 64 kbit/s
*channel id - 18 3 a1 83 9f
interface implicitly identified
other interface type ( e.g. primary rate )
channel preferred
channel is not the D channel
channel as indicated in following octets
CITT coding standard
channel in the following octet
b channel units
channel 31
*calling party number - 6c c 21 83 32 30 37 33 30 36 37 36 34 36
type national number
plan - isdn/telephony
presentation allowed
screening - network provided
Number - 2073067646
*called party number - 70 7 c9 34 39 37 32 34 30
type subscriber number
plan private numbering
Number - 497240

[13:10:22:416] <0001136646> [189494:2]0FEFDF98: RX:00,01,06,08,08,02,80,39,5A,08,02,80,91,
Receive
Port - [189494:2]
Time - [13:10:22:416]
SAPI - 0
C/R - 0
TEI - 0
I-Format
Transmit Sequence Number - 3
Receive Sequence Number - 4
P/F bit - 0
Protocol Discriminator - 8
Call Ref Length - 2
Call Ref Flag - 1
Call Reference - 39
message type - RELEASE COMPLETE
*cause - 8 2 80 91
coding standard - CCITT standard
location - user
class - normal event
cause - user busy


If I take the trunks out of service or reboot the switch, I still get busy when I call in, I would have thought that i would get NU or out of order message?

Thanks again for all support
 
If you see nothing within monitor then it does not reach the ipoffice.

Check the cabling and let someone test the trunk.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
SOLVED!

Thanks for your help and advice.

It turned out to be the 2nd PRI configured for 8 channels and the calls were coming in to the 2nd PRI first, not the first one that was opened for 30.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top