SIP Trunks from 3300 to Exchange

[backr]

I have 9 out of 10 SIP Trunks locked up between a 3300 and an Exchange Voicemail. Does anyone know how to release them? I tried to busy them out and RTS and it did not work

 

[slapin]

SIP trunks are virtual entities. There is no such thing like SIP trunk #2 or SIP trunk #3 connected between two peers. It counts against number of open sessions between INVITE message and acknowledged BYE message.

Check session times in SIP peer profile

Set the SIP session timeout value (in seconds). If the peer does not respond within the allocated time, the session (call) will be torn down. The default is 90. The range is from 90-9999. Set the Session Timer to 0 to disable it.

 

[backr]

I tried that, and no luck
This is what I get when I do a sip show activity all. I would hate to have to do a reboot on the 3300. I already tried a reboot on the exchange sever


1) Link: EXCHANGE Profile: exchange ID: 15e24410(1433)-10019424
Started at WED AUG 05 16:08:54 2009
Calling: 818206@192.168.0.26
Called: 2500@192.168.0.26
State: StateClearingWaitForClearAck
MediaState: StateMediaTerminated (-1,-1)
Call-ID: 943814976-84987884@192.168.3.3
Media Session not present

 

[fissure]

was it:

SIP BUSY PEER EXCHANGE

SIP RTS PEER EXCHANGE

you did?


I've also found, going into the relevant 'Network Element Assignment' and/or 'SIP Peer Profile' and clicking SAVE, even without changing anything, triggers SIP activity/reconnection

 

[slapin]

Hm. The session timer should work.

If you can, try to capture entire SIP session using WireShark and attach the pcap file or send it to me. tvman_us (at sign) yahoo.com

 

[backr]

Thanks for all the help. I had to leave the site and scheduled a reboot for early a.m. I am sure it will happen again.

 

[SXWizard]

You didn't say what software you are running on the 3300. I had no problems with SIP to Exchange 2007 UM on Rel 9.x but after going to MCD 4.0 (Rel 10.0) i have been having the same problem you are. It happens about once a week and so far only a re-boot of the 3300 fixes it. I am waiting for the next failure to open a ticket with Mitel Tech Support.