Bad TTR's?? 1

[Ghostin]

I have a customer with 4 ground start lines coming across a T-1. The rest of the T-1 is two-way DID. The operators use the ground start lines to recieve incoming calls and dial out. Every 6th and 8th call, they can't break dial tone. It is consistant on every line. If I dial out on line 1, on the 6th try I can break DT, then on the 8th Try I can't break DT, then it starts over. They only have a 400 card and 012, so they only have 6 TTR's to begin with. I would have thought if I had a bad TTR, it would be one out of 6 tries. Anyone have any thoughts or suggestions? The provider of the T-1 was out yesterday to test and could not find any problems on thier end.

 

[jinxs]

did you test the TTRs??? Goto any T/R station and dial *04 123456789*0# and you should get the conformation tone....if not, you have a bad ttr. It doesn't hurt to check.

 

[jgideon]

The instructions I have are:
dial *04 and the 2 digit TTR number (starting with 01) of the ttr that you want to test. You'll hear busy if it is inuse, reorder if it doesn't exist.

If dialtone, then dial 123456789*0#, you should hear each tone as it's dialled, then a 3 beep confirmation tone.

 

[merlinman]

Actually, it can be 2 or 3 beeps and still be OK.

NO BEEPS, not good.

 

[comdata]

Speaking of TTR troubles, I have a Legend R6 V11 that displays "all TTR's unavailable" error OC03 starting March 11 and the time stamp is somewhere about 1:45 am. The system has 4-408 GL/LS/MLX cards and 1 016. I tested the 4 TTRs several times thru. The only customer complaint is that they are not able to get thru on the backdoor number at times. Any ideas?

 

[comdata]

I forgot to mention that the Legend is integrated with a Messaging 2000 (Octel 100) unit.

 

[SYQUEST]

Hi warbrat44,

I believe that error code 0C03 for the TTRs occurs when none are available. This can be caused by 4 analogue lines going off hook at the same time or the M2K transfering calls. Then the 5th one would get no dialtone until a TTR became available. If this happens alot this can be a problem, otherwise if the TTRs test good there is nothing physically wrong with the system. To add more TTRs you would have to add a module that is equipped with some like the 016 or the 400 or 800 types. You might check the manual to verify which modules do have TTRs.

Just a note, finally someone else with the Messaging 2K. I take care of one also, with a R6.0 Legend, but have not done any programming on it yet! Do you know if the M2K has remote program capabilities? Can you talk to it with a VT100 terminal via modem?

Hope this helps!

....JIM....

 

[comdata]

Jim, thanks for the heads up. I actually take care of several M2K's and they have been working great. As for remote programming, I haven't tried it yet. I seem to remember that you can access them remotely; I'll have to research it and let you know if I find out anything. As for the TTR's error, I find it curious that they only occur about the time the system does its backup in the early am. Thanks for your input.

Alex

 

[ceo255]

Hmmm, TTRs not available about the time it does it's backup... I will bet it takes all of it's ports offhook, to keep calls from coming into the voicemail system. I don't know how many TTRs your system has but I will bet it's less then the total number of voice mail ports on the system. IE. If the system has 4 TTRs and 8 voicemail ports, when it takes them all offhook, there isn't TTRs available for the last 4 port's analog stations.

 

[comdata]

Thanks mrceo, I think you nailed it! The M2K has 6 VM ports and the single carrier system only has 4 TTR's. Appreciate the heads up, I'll need to make a slight modification.