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!

Has MD110 done his job to provide Inband busy tone for incoming call?

Status
Not open for further replies.

tanhh

Technical User
May 9, 2007
18
GB
System: BC12 SP11 standard APS.

Traffic case:
MD110' extension XXXX is busy.
External VoiceMail system makes a call to this extension XXXX via ISDN PRI (ISO QSIG).

What I want to achieve:
MD110 is suppose to provide Inband busy tone to the incoming call from the external voicemail system.
Voicemail system then can relay the Inband busy tone back to the Calling Party.

Attached is the MD110 parameters and ISDN Signal Trace.

Question:
1. MD110 sends PROGRESS message to indicate Inband information is available in Progress Indicator IE. What should the voicemail react upon receiving the PROGRESS message from MD110? In the signal trace, MD110 DSICONNECT after

2. What is the duration for the inband busy tone? Who control the duration? The A-party in VoiceMail system or the timer in MD110?

3. MD110 subsequntly sends DISCONNECT message 160 milliseconds after sending Progress message. Has MD110 done his job in providing the Inband Busy Tone? If yes, why the duration is so short (160 millisecond)? Human ear can not detect such a short period?

4. Is the Inband Busy Tone mean for VoiceMail system for call control purpose or mean for Human to listen?


<ROCAP:ROU=102;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
102 7130000000000010 5 3110000001 0 30 128 00020215 111110100031 111111

END

<RODAP:ROU=102;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
102 SL60 H'00200250 H'15440000 H'06300000 NO

END

<RODDP:DEST=100;
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
100 102 1606100000000250106001101 0 1 0

END

<
19.09.50.880 00023 HWSW SIGNAL DLIDATALONG (H'0002)
FROM EQU NO 8-1-70-00
TO SLP60 (H'037B) EXE A IN LIM 008
WITH 0 1 2 3 4 5 6 7 8 9
000 H'01 H'00 H'08 H'02 H'00 H'08 H'05 H'04 H'03 H'80
010 H'90 H'A3 H'18 H'03 H'A9 H'83 H'9F H'70 H'05 H'80
020 H'35 H'34 H'39 H'38 H'00 H'00 H'00 H'00 H'00 H'00
030 H'00 H'00



>>>>
Incoming Message: SETUP
Call Reference: 00 08 (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 RateCircuit Mode: 64 kbits
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
PreferredExclusive: Exclusive; only the indicated channel is acceptable
D-channel Indicator: The channel identified is not the D-channel
Information Channel SelectionPrimary 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: 31



CALLED PARTY IE:
Type of Number: Unknown
Numbering Plan Identification: Unknown
Called Number: 5498


<<<<

19.09.50.940 00033 SWHW SIGNAL DLRDATALONG (H'00A1)
FROM SLP60 (H'037B) EXE A IN LIM 008
TO EQU NO 8-1-70-00
WITH 0 1 2 3 4 5 6 7 8 9
000 H'08 H'02 H'80 H'08 H'0D H'18 H'03 H'A9 H'83 H'9F
010 H'02 H'05 H'0F H'4E H'02 H'05 H'1E H'36



>>>>
Outgoing Message: SETUP ACKnowledgement
Call Reference: 00 08 (CR Flag Set)
Protocol Discriminator: Q.931 user-network call control protocol



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
PreferredExclusive: Exclusive; only the indicated channel is acceptable
D-channel Indicator: The channel identified is not the D-channel
Information Channel SelectionPrimary 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: 31


<<<<

19.09.50.960 00035 SWHW SIGNAL DLRDATALONG (H'00A1)
FROM SLP60 (H'037B) EXE A IN LIM 008
TO EQU NO 8-1-70-00
WITH 0 1 2 3 4 5 6 7 8 9
000 H'08 H'02 H'80 H'08 H'02 H'02 H'05 H'0F H'4E H'02
010 H'05 H'1E H'36



>>>>
Outgoing Message: CALL PROCeeding
Call Reference: 00 08 (CR Flag Set)
Protocol Discriminator: Q.931 user-network call control protocol





<<<<

19.09.50.980 00036 SWHW SIGNAL DLRDATALONG (H'00A1)
FROM SLP60 (H'037B) EXE A IN LIM 008
TO EQU NO 8-1-70-00
WITH 0 1 2 3 4 5 6 7 8 9
000 H'08 H'02 H'80 H'08 H'03 H'1E H'02 H'81 H'81 H'02
010 H'05 H'0F H'4E H'02 H'05 H'1E H'36



>>>>
Outgoing Message: PROGress
Call Reference: 00 08 (CR Flag Set)
Protocol Discriminator: Q.931 user-network call control protocol



PROGRESS INDICATOR IE:
Coding Standard: CCITT standard
Location: Local private network e.g., PBX
Progress Description: Call is not end-to-end ISDN; further call progress information may be available in-band. Interworking with a non-ISDN has occurred within the network or networks which the call has traversed.


<<<<

19.09.51.140 00038 SWHW SIGNAL DLRDATALONG (H'00A1)
FROM SLP60 (H'037B) EXE A IN LIM 008
TO EQU NO 8-1-70-00
WITH 0 1 2 3 4 5 6 7 8 9
000 H'08 H'02 H'80 H'08 H'45 H'08 H'02 H'81 H'91 H'1C
010 H'23 H'9F H'AA H'06 H'80 H'01 H'00 H'82 H'01 H'00
020 H'8B H'01 H'00 H'A1 H'15 H'02 H'01 H'01 H'02 H'01
030 H'03 H'80 H'0D H'48 H'6F H'6F H'69 H'20 H'48 H'6F
040 H'6E H'67 H'20 H'54 H'61 H'6E H'02 H'05 H'0F H'4E
050 H'02 H'05 H'1E H'36



>>>>
Outgoing Message: DISConnect
Call Reference: 00 08 (CR Flag Set)
Protocol Discriminator: Q.931 user-network call control protocol



CAUSE IE:
Coding Standard: CCITT standard
Location: Local private network eg PBX
Cause Value: Normal event
Cause Values, CCITT Standard: User busy


FACILITY IE:
Type of Protocol: ISO
Network Facility Extension
Source Entity: (0) End PINX
Destination Entity: (0) End PINX
Interpretation APDU: (0) Discard any unrecognized Invoke PDU
Type of component: Invoke PDU
Invoke ID: 1 (H0001)
Type of Service: Busy Name
Name Presentation Allowed Simple: H48 H6F H6F H69 H20 H48 H6F H6E H67 H20 H54 H61 H6E 'Hooi Hong Tan'


<<<<

19.09.51.180 00039 HWSW SIGNAL DLIDATALONG (H'0002)
FROM EQU NO 8-1-70-00
TO SLP60 (H'037B) EXE A IN LIM 008
WITH 0 1 2 3 4 5 6 7 8 9
000 H'01 H'00 H'08 H'02 H'00 H'08 H'4D H'08 H'02 H'80
010 H'91 H'00 H'00 H'00 H'00 H'00 H'00 H'00 H'00



>>>>
Incoming Message: RELease
Call Reference: 00 08 (CR Flag Not Set)
Protocol Discriminator: Q.931 user-network call control protocol



CAUSE IE:
Coding Standard: CCITT standard
Location: User
Cause Value: Normal event
Cause Values, CCITT Standard: User busy


<<<<

19.09.51.180 00043 SWHW SIGNAL DLRDATALONG (H'00A1)
FROM SLP60 (H'037B) EXE A IN LIM 008
TO EQU NO 8-1-70-00
WITH 0 1 2 3 4 5 6 7 8 9
000 H'08 H'02 H'80 H'08 H'5A H'02 H'05 H'0F H'4E H'02
010 H'05 H'1E H'36



>>>>
Outgoing Message: RELease COMplete
Call Reference: 00 08 (CR Flag Set)
Protocol Discriminator: Q.931 user-network call control protocol





<<<<
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

 
The valid ISDN signalling in the case of sending Inband Busy Tone at Incoming call is depicted below:

1. PABX sends Progress indicator No 8 (Inband information available) in PROGRESS MESSAGE to indicate PABX has inband tone.
2. Next PABX send DISCONNECT, Timer T305 started.
3. Timer T305 will only stop if A)30s elapsed or B) Receive RELEASE from Voice Mail.
4. 30s elapsed or received RELEASE.
5. PABX sends RELEASE COMPLETE.
6. The B-channel return to Idle Free state.

So PABX has done his job.

The problem is that Dialogic does not react to the Progress Indicator value in DISCONNECT message correctly. Indeed it immediately sent Release to PABX which is wrong. The A-party can not hear hear a 40 milliseconds busy tone.

Conclusion for the Inband Information Issue:
Dialogic does not react to the Progress Indicator value in DISCONNECT message correctly.

It should have started the timer T305 (30s) before sending RELEASE to PABX, instead of sending RELEASE immediately.

This will allow A-Party to hear Busy Tone for 30s.

Basically:
If DISCONNECT without Progress indicator 8 sent, timer T305 (30s) shall be started.
If DISCONNECT with Progress indicator 8 sent, timer T306 (3s) shall be started.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top