SIP trunk drops after about 10 secs on hold.

[x-man]

Bit of an awkward one this....but maybe someone has seen simolar.

Mitel 3300 CX connected to SIP trunks via a firewall (which i don't control) to Hipcom trunks. Everything seems to be fine except hat when you do a consultation hold (transfer) if you leave it for longer than about 10 secs (whilst talking or letting it ring)the SIP trunk disconnects and you get "there is a fault" announcement from the line.

If the transfer is dealt with withing that time then everything is OK, you can retrieve the call if need be or complete the transfer and its OK, its just like there is a timer forcing the call out except for I would expect a NU tone or reorder tone from the network ratehr that he fault report being given out ?

Anyone any ideas? Trunk provider are blaming the firewall.....

[x-man]

Just a bit more testing info on this. Hold works fine, can put on hold and retrieve after 30 secs.....so it looks like its just down to consultation hold.....

[x-man]

after further testing hold is NOT working on Minet phones (Hold and transfer hold drop out after about 20 seconds) BUT works fine on some SIP sets (we think as we have to transfer an incoming call to the SIP sets to test).

Anyone any ideas because it looks like a 3300 problem.

Please

I'm going to cross post to the other mitel forum as well just in case anyone there is not on here.

[x-man]

and I think I may have found the answer just before I read it on the other forum. Will report back here if it works when we test it.

[johnp]

I would try not sending hold to provider

[martyn]

Do you have MoH running?

I would say that it is not sending the correct responses when the call is placed on hold, and so the carrier detects no audio stream and drops the call.

[ralph]

I would say that it is not sending the correct responses when the call is placed on hold, and so the carrier detects no audio stream and drops the call.

There's something I wouldn't have thought of.  Isn't there a heartbeat timer?

I'd actually bet, though, that it's the "avoid signaling hold to carrier" setting in the peer profile.

Ralph

[x-man]

indeed, I found it yesterday whilst trolling through the SIP testing notes from Hipcom and then found the setting in SIP peer profile, just need to get back to site to test it now.