Not receiving the disconnection signal

rated by 0 users
This post has 2 Replies | 3 Followers

Top 100 Contributor
Female
Posts 55
Points 860
Sajeewani Thennakoon Posted: 03-17-2010 6:31 AM

Hi ,

We have installed a Dialogic DMIP601 card in one of our customer sites. The telco operator has provided us an ISDN line.

Upto yesterday the system worked without any problem, but from yesterday we are expereinecing a preculier problem.
Even when the caller disconnects the call, we are not receiving the disconnection signal. Instead we are receiving a beep tone for few seconds (around 20) and there after we are receiving the disconnect signal. The status monitor also shows the call as connected. So our system proceeds futher even after the call disconnection, and in result it makes several disturbances in the operation.

Please let us know any thing to be look into from our side.

 

Thanks.

Sajeewani.

  • | Post Points: 20
Top 10 Contributor
Posts 823
Points 12,380
Dialogic Employee

Sajeewani,

1.  If the call was originated by the application, this may be a normal service, where TELCO doesn't disconnect the remote party immediately. 20 sec sound like a usual grace timeout. If the switch provides such feature it sometimes first sends FACILITY message followed by DISCONNECT after the timer expires.

Q: Where the call under question was originated from? Do you see GCEV_FACILITY or any other GlobalCall event around a time of remote disconnect?

2. Can you describe this beeping pattern in more details? You may need to add this tone definition in order to be able to recognize it and drop the call locally when the tone presents.

3. In ISDN when one of parties hangs up, the second party should receive DISCONNECT message. It results in GCEV_DISCONNECT event in your application. ISDN as a protocol doesn't rely on audio tones.

Q: Why does the app need to recognize the Disconnect tone instead of relying on a digital DISCONNECT message? IS DISCONNECT message ever provided by the switch?

You may want to discuss the questions above with your network provider first. Please also capture an ISDN trace on the board (vi "isdntrace -bx -dy" command) and attach it to your next post.

 

Thanks, Leonid
  • | Post Points: 20
Top 100 Contributor
Female
Posts 55
Points 860

Thanks a lot for your feedback.

1.The call was not originated by the application. It was an inbound call from the TELCO side. We cannot see GCEV_FACILITY either.

2. As this is ISDN, no need to worry about the beep pattern as you have mentioned.

3Q. We are not relying on disconnect tone. We are expecting the disconnect signal. The problem is, we are not receiving the disconnect signal as soon as the call disconnects. There is an about 20 sec delay for that signal to come.

Currently we are talking with TELCO as well, and looking for their reply also.

  • | Post Points: 5
Page 1 of 1 (3 items) | RSS