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!

Q.931 ISDN Trace

Status
Not open for further replies.

Jeppedal

Technical User
Aug 13, 2002
58
NO
Hi!

I am not familiar with the Nortel Meridian, but have some experience with other systems. Is there any way of making traces for incomming/outgoing ISDN/QSIG/Q.931 traffic on a trunk? The best thing would be if I could get info about SETUP, CALL PROCEED, etc in plain text ... Could anyone please tell me how to initiate it?

Best regards
Paal E. Jeppedal
 
Hi...
For tracing an isdn... U need to..

LD 96

ENL MSGO X (Outgoing)(X is the D-channel number)
ENL MSGI X (Incoming)

Please take note that... If the traffic for the qsig or isdn lines are too heavy, do not attempt to turn on... as it will INI the system....
 
Hi!

Thanks for your response. I was able to do my traces, even if I think the format was a little bit cryptical ...

This is an example of what I get out of my other systems:

Best regards
Paal E. Jeppedal



Outgoing Message: SETUP
Call Reference: 04 77 (CR Flag Not Set)
Protocol Discriminator: Q.931 user-network call control protocol

BEARER CAPABILITY IE:
Coding Standard: CCITT standardized
Information Transfer Capability: Speech
Transfer Mode: Circuit-mode / Call independent signalling connection
Information Transfer Rate/Circuit Mode: 64 kbit/s
Layer 1 Protocol Identification: User information layer 1 protocol
Recommendation G.711 A-law

CHANNEL ID IE:
Interface Identifier Present: Interface implicitly identified; the interface which includes the D-channel carrying this information element is indicated.
Interface Type: Primary rate interface
Preferred/Exclusive: Indicated channel is preferred
D-channel Indicator: The channel identified is not the D-channel
Information Channel Selection/Primary Interface: As in following octets
Coding Standard: CCITT standard
Number: Channel is indicated by the number in the following octet
Channel Type: B-channel units
Channel number: 14

PROGRESS INDICATOR IE:
Coding Standard: CCITT standard
Location: Local private network e.g., PBX
Progress Description: Originating address is non-ISDN

CALLING PARTY IE:
Type of Number: National Number
Numbering Plan Identification: ISDN numbering plan
Presentation Indicator: Presentation Allowed
Spare, reserved
Screening Indicator: User provided, verified and passed
Calling Party Number: 24044840

CALLED PARTY IE:
Type of Number: Unknown
Numbering Plan Identification: ISDN numbering plan
Called Number: 1922790125680
 
Hi....
ur one looks a bit strange maybe because u are using q.931 B-channel signalling. I am actually using D-channel and everythings looks as per what u like... like call setup... call proceed... call connecting...

DCH 10 IMSG ALERT REF 0000000D CH 8 13 TOD 10:11:00
FEAT :NAS

DCH 10 IMSG CONNECT REF 0000000D CH 8 13 TOD 10:11:00

DCH 10 OMSG CONN ACK REF 0000000D CH 8 13 TOD 10:11:00

DCH 10 OMSG DISC REF 0000000D CH 8 13 TOD 10:11:02
CAUSE :NORMAL CALL CLEARING

DCH 10 IMSG RELEASE REF 0000000D CH 8 13 TOD 10:11:02

DCH 10 OMSG REL COMP REF 0000000D CH 8 13 TOD 10:11:02
 
Hi!

Your example gives the same information as I got from my Meridian. Is it possible to get more extended information from the SETUP message on calling / called-party, numbertypes, actual number, etc ...?

Best regards
Paal E. Jeppedal
 
hi....
the details i give u is just a normal tie line details. as for isdn, u should be able to see the full information.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top