SIP trunk with cisco - audio stopped after 15 minutes

[vorlander]

Hi to all, we have a sip trunk between mitel mxe platform and a cisco call manager.

Everythink work fine, but we have a problem that after 15 minutes the audio is stopped.

Have someone experienced this problem?

Thank you

[ralph]

What version of 3300 are you using?
Is the audio uni-directional or can nobody hear anybody?
Have you done a Wireshark Sniff to check out the packets?

Ralph

[vorlander]

The 3300 version is 9.0, and when the problem appear nobody can hear nobody.
No, we haven't done any capture, i suppose that someone have alredy see this problem and can help us

[Chakara]

  I'd seriously try to upgrade the 3300 - Mitel has made a lot of improvements to SIP since version 9.

-Chak

[wonderboy]

Did you find a solution to this?   I am having the exact same problem.  Thanks

[brantn]

Yes I would recommend at least upgrading to 4.0 they have fixed a lot of the mid call signaling issues since 9.0.

[Dumptrick]

I hate to bring back an old Thread but a Google search brought me to this. 

I'm having the same issue amd I'm running 4.2 SP2 on a 3300.  Is there a call length timer somewhere?

[v2win]

Try setting the session timer to 0

[MrVOIP]

I've seen this question come up several times, but haven't seen anybody answer it - correctly.  The answer is actually in the Mitel documentation for configuring SIP trunks with Cisco Call Manager.  Drove me nuts on our in-house demo system until we actualy had someone RTFM.

There are two settings in the MCD SIP Peer Profile page that are set to "No" by default.  They must be enabled (Set to "Yes") 

1.  On the "SDP Options" tab

• Repeat SDP Answer if Duplicate Offer Is Received      YES

(This is set to no by default)

2.  On the "Signaling and Header Manipulation" tab

• Disable Reliable Provisional Responses    YES

(This is set to no by default)

This will stop the loss of audio after 15 minutes. 

[ralph]

Thanks for the ping on this.
Mental note made.

Ralph

[martyn]

Yep I'll be storing that one away as we are doing more and more 3300 to CUCM integrations.