Dialogic Presents Busy Tone

[Guest miva]

This system was working well until I unplugged the On Ramp and then went to plug it back in again. Seems to be that either Dialogic Card or the On-Ramp aren't all that stable if disconnected from one another.

 

VoiceGuide Status Monitor also informs me that Device 1 is "Blocked" but the remaining lines are Waiting for a Call. Any ideas?

 

I made a call from the system using ISDIAG and then tried to call the system using ISDIAG. When I call into the system it gives me a busy tone.

 

Log from ISDIAG.

 

PROTOCOL TYPE : PRI NET5

TRACE START TIME (MM/DD/YYYY) : 3/29/2007, 15:57:50.656

 

Time Stamp : 3/29/2007, 15:58:18.696

TRANSMIT

Command=0 SAPI=0x00

TEI=0x00

0x7f Set Asynchronous Balanced Mode

 

 

Time Stamp : 3/29/2007, 15:58:19.696

TRANSMIT

Command=0 SAPI=0x00

TEI=0x00

0x7f Set Asynchronous Balanced Mode

 

 

Time Stamp : 3/29/2007, 15:58:20.696

TRANSMIT

Command=0 SAPI=0x00

TEI=0x00

0x7f Set Asynchronous Balanced Mode

 

 

Time Stamp : 3/29/2007, 15:58:21.696

TRANSMIT

Command=0 SAPI=0x00

TEI=0x00

0x7f Set Asynchronous Balanced Mode

[Guest miva]

Another file that shows the system information is attached

sys_inf.zip

[SupportTeam]

VoiceGuide Status Monitor also informs me that Device 1 is "Blocked" but the remaining lines are Waiting for a Call. Any ideas?

Most likely the communications D channel has not been established.

 

I made a call from the system using ISDIAG and then tried to call the system using ISDIAG. When I call into the system it gives me a busy tone.

When you open ISDIAG do you see the D channel indicator as showing that the D channel is present? (it's one of the status indicators in top right corner)

All status indicators should be 0.

Consult the ISDIAG documentation on these report flags.

 

If D channel is not present then you should contact the E1 line supplier and ask them why is the E1 disabled...

[SupportTeam]

Looks like file did not attach - could you try attaching it again to a new post?