Jump to content

pressing mute on snom360 disconnects call after several seconds


mattlandis

Recommended Posts

Snom 360 -snom360-SIP 7.1.35 14552

I think 7.1.35 gve us troubles with 1-way audio. We experienced 1 way audio, and a quick hold and unhold fixed this 1 way audio problem. We downgraded 1 release. This was late last summer or early fall. 7.3.14 is now on all phones.

Link to comment
Share on other sites

I think 7.1.35 gve us troubles with 1-way audio. We experienced 1 way audio, and a quick hold and unhold fixed this 1 way audio problem. We downgraded 1 release. This was late last summer or early fall. 7.3.14 is now on all phones.

 

Thanks for that input.

 

if you think what that audiocodes parameter is let me know...that is likely the problem...because only calls thru audiocodes does it...

 

(this problem doesn't cause us a lot of pain...but a client would not put up with it.)

 

tx

matt

Link to comment
Share on other sites

if you think what that audiocodes parameter is let me know...that is likely the problem...because only calls thru audiocodes does it...

 

(this problem doesn't cause us a lot of pain...but a client would not put up with it.)

 

Do you get a admin email about the disconnect? That would be a clear sign that the PBX thinks the call dropped. Also, check if the AudioCodes has VAD turned on (turn it off if that should be on).

Link to comment
Share on other sites

Do you get a admin email about the disconnect? That would be a clear sign that the PBX thinks the call dropped. Also, check if the AudioCodes has VAD turned on (turn it off if that should be on).

 

No admin email.

 

Still looking for that VAD (voicd activation detection) setting...these audiocodes. ..;-)

 

tx

matt

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 months later...
i am having the same issue and it seems it has to do with snom, since my 2 polycoms conference phones work just fine. i too have an audiocodes gateway.

 

The snom disconnects after 10 seconds.

 

This is almost a "FAQ"... What firmware are you using? I was under the impression that newer firmware versions fix that problem.

Link to comment
Share on other sites

7.3.14

 

Using the latest software 3.3.1.3177

 

Does this happen only on the conference calls or even a call from snom360 to other phones? I am assuming you are pressing mute on the snom 360 and not the other party. Tested it here on the same version (7.3.14) and the problem did not happen. Maybe a wireshark trace will tell us how is disconnecting the call.

Link to comment
Share on other sites

This only happens when with a call to the outside like a cell phone. when calling another snom phone internally, it is fine. the snom phone reports this in the log:

[5]30/4/2009 11:47:30: Dialog 7/8 going to trying

[5]30/4/2009 11:47:30: Dialog 7/8 going to early

[5]30/4/2009 11:47:33: Dialog 7/8 going to confirmed

[5]30/4/2009 11:47:55: Dialog 7/8 going to terminated

[5]30/4/2009 11:47:56: timeout::callback: Registering with timeout of 0 ms

[5]30/4/2009 11:48:17: Settings applied!

[2]30/4/2009 11:48:33: Registered at registrar as 321@localhost (Expires: 179 secs)

 

this is what my audiocodes is reporting:

 

11d:14h:37m:6s ( lgr_psbrdex)(375420 ) recv <-- acEV_BROKEN_CONNECTION, Ch:2

11d:14h:37m:6s ( lgr_flow)(375421 ) #2:RTP_BROKEN_CONNECTION_EV

11d:14h:37m:6s ( lgr_flow)(375422 ) | #2:RTP_BROKEN_CONNECTION_EV

11d:14h:37m:6s ( lgr_flow)(375423 ) | #2:MANUAL_DISCONNECT_CALL_EV (send) : (f0c802a0@pbx)

11d:14h:37m:6s ( lgr_flow)(375424 ) | | #2:MANUAL_DISCONNECT_CALL_EV:(f0c802a0@pbx)

11d:14h:37m:6s ( lgr_flow)(375425 ) | | #2:Call changing states from:ConnectedState to:DisconnectingState

11d:14h:37m:6s ( lgr_flow)(375426 ) | | #2:RELEASE_EV:(f0c802a0@pbx)

11d:14h:37m:6s ( lgr_flow)(375427 ) | | #2:Call changing states from:DisconnectingState to:DisconnectingState

11d:14h:37m:6s ( lgr_flow)(375428 ) | | #2:RELEASE_ACK_EV:(f0c802a0@pbx)

11d:14h:37m:6s ( lgr_flow)(375429 ) | | | #2:RELEASE_EV(f0c802a0@pbx)

11d:14h:37m:6s ( lgr_flow)(375430 ) | |(SIPTU#1)DISCONNECT_REQ State:Connected(f0c802a0@pbx)

11d:14h:37m:6s ( lgr_flow)(375431 ) ---- Outgoing SIP Message to 192.168.2.19:5060 from SIPInterface #0 ----

 

I will get the wireshark trace, although i am seeing alot of "UDP Checksum errors" in wireshark at the moment

 

is this normal?

Link to comment
Share on other sites

  • 2 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...