timeout error 1

[macphoneguy]

it seems if I make a call specifically using a trunk aka LS/GS card it doesn't seem to matter where the call orginates from i.e. made or recieved from the Mitel after approximatly 3 minutes, the display changes to "time out error" and a quick busy signal, If I make a call using a butt set on the same Tunk to that same number everything is fine where to start ?

 

[MitelInMyBlood]

Start in Class Of Service for the trunk. Call Duration Forced Cleardown Timer. Make it zero.

 

[macphoneguy]

I checked it is set to Zero

 

[T8keiteasy]

What about "Enable Call Duration Limit on External/Internal Calls" and "Call Duration" on COS ?



Now, it's about French users too !!!

 

[kwbMitel]

I doubt that it will be call duration settings as these give warnings and specific display messages that do not look like above. That being said, it wouldn't hurt to check anyway.

Another thing to check might be your answer supervision settings. If they are set to expect answer supervision and none is provided the system might be treating the call as unanswered and clearing it down. This is just a guess. This trouble is strange.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[macphoneguy]

if it helps the call can be answered, and both partys can talk till the display says timeout and hangs up, and in referance to the Enable call duration internal/external are No in the COS, I checked other analog trunks with the same results at the 3 minute mark "timeout" and quick busy

 

[Mitelmatt]

sounds like what kwbmitel says, check for answer supervision

The system is probably not receiving answer supervision from the central office and is timing out.
If the Central office cannot provide answer supervision on answered calls go to the CO Trunk Circuit Descriptor Assignment and change the value in the field"fake answer supervision after outpulsing" to yes.

 

[nytalkin]

check to see if you have a final tone plan defined in the route...if so remove it and try the call again.

NO GOOD DEED GOES UNPUNISHED!

 

[macphoneguy]

it was the CO trunk Descriptor had to change the fake answer supervision to yes, and then changing the trunk descriptor under trunk assignment and then it worked
Thanks to Mitelmatt ;-)

 

[kwbMitel]

Well done Matt, Where did you possibly come up with that one? ;-)

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelmatt]

what a team kwb!! :)