Mediatrix 2102 problems

[Ceaserx]

Since upgrading the 3300 Mxe controller to Version 9 at a client we have ongoing problems with the mediatrix devices. They just lock up stating trunk busy when trying to phone them. The only way i have managed to get them working again is by deleting the Sip peer profile and Network element and recreating, but now some of them just get the same issue a day or two later.

Is their a way to busy and release the "trunk" for these devices? Any other ideas what can be causing this problem?

 

[eng3alaa2299]

you can use this 2-comanad to make it busy

1-SIP BUSY PEER <PEER_NAME>
Examble:
sip busy peer SoftSw2A

SIP BUSY ( COURTESY ) PEER SoftSw2A succeeded.

Link state changes from IDLE to MAN BUSY.
--------------------------------------------------
2- SIP BUSY FORCE PEER <PEER_NAME>
Forces busy on the designed peer name. The calls in progress are dropped.
-------------------------------------------------------
and you can use this command to Return it to service

SIP RTS PEER <PEER_NAME>
Returns the busied peer to service.

Example:

sip rts peer SoftSw2A

SIP RTS PEER SoftSw2A succeeded.

Link state changes from MAN BUSY to IDLE.
----------------------------------------------------------
and You can use this command to check the link status;

SIP LINK STATE PEER <PEER_NAME>
Displays the link state for the selected peer name.

The state can be one of:

"IDLE" - Initial state; no calls have been made on the link.

"IN SERVICE" - The link is in service.

"OUT OF SERVICE" - A temporary or permanent network outage/error was detected on the link.

"VALIDATING" - A new call is being attempted and is bringing the link from OUT OF SERVICE to IN SERVICE, if possible.

"MAN BUSY PENDING" - The link is being busied out, and no new calls can be made. One or more existing calls are still up.

"MAN BUSY" - The link is busied.

"UNKNOWN" - Unexpected error on the system

I hope it's will help you

 

[Ceaserx]

thanks!

Very helpful

 

[eng3alaa2299]

Happy it's help and You are Always wellcome