Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Voice Messages of 30 Second worth of dial tone

Unity 4.1, Centrex Integration, exchange 2000 off box.

A user has been experiencing several vm msgs of 30 worth of dial tone. He has received good msgs between these odd msgs. I see nothing in the event logs.

Any ideas?

Thnaks

3 REPLIES

Re: Voice Messages of 30 Second worth of dial tone

There was an issue where CCM would not tear down a call immediately after receiving disconnect from the PSTN. The problem is fixed in TSP 8.0(2) and later. Take a look at Bug CSCsb42730.

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsb42730

Hope this helps.

Brandon

Cisco Employee

Re: Voice Messages of 30 Second worth of dial tone

By default Dialogic does not consider dialtone to be a disconnect event. The built-in disconnect tones that dialogic looks for are candence tones that would match most any Busy or Re-order (fast-busy). My guess of what is happening is the phone system is sending 30 seconds of dialtone before transitioning to re-order. Once the re-order is recieved Unity drops the call.

Ideally, the phone system would send a positive disconnect event, such as loop-current reversal, so that we don't have to worry about call progress tones for disconnect. However, you can fine tune the tone definitions (specifically, add dialtone as a disconnect tone) using the switch INI file in Unity.

Have a read through this document before you do anything though,

Cisco Unity Tone Definitions and Learn Tones

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_tech_note09186a0080093c1e.shtml

Regards,

Eric

New Member

Re: Voice Messages of 30 Second worth of dial tone

FWIW, we suffered through six years of trying to get the integration properly working with the Dialogic / PBXLink devices and we never felt like we had it one hundred percent correct. We achieved a tolerable level of weird behavior, but that was as good as it got. To be fair, much of that time was spent on older ActiveVoice versions of Unity, and things got a lot better with Cisco's 4.x versions.

Last year, on the advice of the Seattle BU, we switched our integration method to pure Call Manager, which is linked back to our PBX (in our case an Avaya S8700) with a T1 line running QSIG. The new integration has worked flawlessly and we have not looked back.

I realize this would be a huge undertaking, but we feel that at least in our environment, it was well worth it.

112
Views
0
Helpful
3
Replies