sundance-communications.com/forum Forums TDM Business Telephone Systems Toshiba Telephones & Systems Toshiba DK 280

I have a customer who has a toshiba DK280 with an "A" processer and one expansion cabinet. The system has a Contact DK 2 port voice mail system. First problem: When two insde extensions add an outside party to a conference call, one of the inside extentions becomes garbled. This happens on all three way conference calls from any extension. The second problem:. multi extensions when left a message and the message key is pressed to retrieve the message the message key sends them into the part of the voice mail system where it say's. 'if you know the first three letters of the persons last name", instead of into their mailbox prompt.Any ideas why these problems occur?

Contact DK uses "9" for directory and uses "*" and "#" in the VMID codes instead of the Strata "91" and "92" - sounds like someone reset the VMID's following the pages in the Toshiba User Guide.

reset the VMID codes at each extension with

<Intercom> #656 #MMM <Redial> <Speaker>
and
<Intercom> #657 *MMM <Redial> <Speaker>
, where MMM is the mailbox (extension) number.

Don't know about the garbled conferencing.

I'm surprised about the expansion cabinet - I always thought that the "A" processor supported only the base cabinet, and that at least a "B" was required for expansions.

welcome to the board!

The toshiba DK system is not the best for long conference calls, as volume has always been an issue. The other is an integration issue... the wrong 656 code is in there

"A" processor one cabinet..wrong customer, sorry!.thanks for the quick responce.I believe I tried resetting the ID codes with same results, but will try again. I also noticed in program *32 someone added the main V.M. extension to some of the extensions having the problem, but not all the extensions. Could not delete it. Other extensions without the trouble are blank in program *32

jknichols,

sorry for the post over yours... I was typing while you posted.



----

ceaser ,

*32 should be the same for all ports : either blank or the first port of VM.

You may have to initialize *32 and reprogram too. It's a process that we can't post in the open forum, only via PM... since it's not user-level programming.

Update:...thanks for info.
I went to customer site and programmed the ext. with the msg button retrieval issue. I programmed in the 656 and 657 as instructed. This was the out come: when I called the main number and the operator transfered me to the ext. instead of it going into his voice mail it kept going into a canned msg loop."please wait while I try that ext....rings three times at the phone and keeps repeating the same canned msg over and over.The display say's CF/BA 216...but continues in that canned loop. I removed those ID codes via 604 and it started to recieve msg's. But the msg key would not go into his voicemail. I used the 565 91 and 657 92 for voicemail fowarding at the phone. I am not sure what you mean by "PM" personal mail?. The conference issue I tested with one inside ext and two outside land callers and still the inside ext hears the two conferenced calls very fussy...unaudable only to the inhouse user.(lawfirm) Outside callers not affected.Three new lines were added to customer site to existing truck card, I also added a new station card to max out the cabinet. Did not use a port ext. for testing calls on conference from new card. I will try and remove the card off hours and see if the trouble clears up and let you know. Sorry for the long post but I see from other post you like as much info as you can get for your best possible diagnoses of the troubles

I figure you meant 656 91.

As the earlier post indicated, #656 91, and #657 92 are incorrect for that voicemail system.

So for ext 234, enter "#656#234" and "#657*234"

CF-BA indicates you used the #604 (Busy/No-Answer) CF code. #603 (No-Answer only) displays as CF-NA.

Clearing the #60X code does not remove the integration codes (#656# and #657*), it only turns of CF.

PM means Private Message, ( click here ) for the FAQ explanation of a PM.

The CNF situation is not uncommon, but should not be so severe that it is inaudible to the calling party. Are you doing the CNF via the CNF/TRNS button or a 3-way calling feature (via Flash Key)? As I stated before, the DK series was never meant to be a CNF solution. If you do a lot of CNF calls, I would suggest the use of a CNF bridge or an amplified solution.

No apology necessary, the more information... the better!


newtecky is correct, you need to use # and * for the Contact DK integration codes.

Just to expand the VMID explanation a bit:

the #656 codes are what your phone sends to the voicemail when it transfers a caller to your mailbox - if people calling your extension are leaving messages properly, then this is probably OK

The #657 codes are what your phone sends to the voicemail when you press the message button. If the only problem is getting thru when pressing the message button, this is where I would start looking.

Also, if you have a separate PhDN button in addition to the standard "Intercom" DN, I believe each path stores its own set of VMID codes.

JK, You're correct on the multiple ID Codes, BUT it depends on your software version as to whether you can actually have PhDN's. Also, if these problems have been fairly constant with this processor it may be an issue that was inherent with that version. I know that 2T had alot of issues.