Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

UCA 4.0 Client Disconnect Issue

Status
Not open for further replies.

TrunkMan

Programmer
Jan 12, 2010
102
GB
Have a problem on UCA4.0. A call comes into t 3300(trunk gateway) and passed on a 3300server(user gateway) via IP trunk. The phone user has set all calls to go through to his softphone(Call forward always from deskphone to softphone). If an external party rings in and decides to disconnect before the call is answered, the softphone continues ringing and all call control is lost. Only way to disconnect the softphone is either restart it or ring the softphone from another mitel phone and then disconnect(i.e bring call control back and then disconnect and all clears down) Any ideas ?
 
Are you getting disconnect supervision from your CO?

As an a side I would use a personal ring group for the above or at least add the deskphone as a key appearance on the softphone.

The single biggest problem with communications is the illusion that it has taken place.
 
Ive tried the key appearance option and still didnt work. The 3300 also generates a msg when the fault happens "badly formatted mitai msg". Also on the ucc.log file there is a msg:

FaultException<ErrorValue>=System.ServiceModel.FaultException`1[Mitel.Communicator.WebServices.CSTA.ErrorValue]: com.mitel.ws.csta.CSTAMBus#CSTAAnswerCall: MBus failed: Response code: 1241 (Fault Detail is equal to Mitel.Communicator.WebServices.CSTA.ErrorValue).

MitaiCall: OnCallControlFailed!!! - Result=noCallToAnswer
 
If you call locally to the UCA does it function normally?

The single biggest problem with communications is the illusion that it has taken place.
 
Yes, works fine internally. Only hangs when calls coming in from PSTN.
 
Interesting...PRI calls or copper?

The single biggest problem with communications is the illusion that it has taken place.
 
Something similiar but it was a while ago so I am fuzzy on the details. If internal works fine then it has something to do with the trunks. Just not sure what.

The single biggest problem with communications is the illusion that it has taken place.
 
Have a look at the COS on your IP Trunks and ensure that Public Trunk is set to no, I have seen similar issues although not with UC where the messaging between the systems is limited due to this setting.
 
Could this be COS option "suppress simulated ccm after ISDN" ?
If so, where would I need this option enabling ?
 
4.0.27 was released a couple of days ago and improves the speed of pop ups etc, there is no new client so if you are on 4.0.26 then a 2 min server blade upgrade is all you need. It has improved our inhouse solution massivly
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top