MCD6.0 SP1 SIP Trunks

[matthew]

I've just been advised by the boffins that this release needs a couple of tweaks to the SIP trunk config to avoid possible issues with outgoing calls. Do this for all SIP Trunks/carriers and test.

a> Set the min. reserved call license to 0, on the basic tab of the associated SIP Peer Profile.
b> Do NOT set overlap out-pulsing for any routes for SIP trunk. ie. "Digit before out-pulsing" should be blank.

[sarond]

Got the same.

Although I always practice
b>  Do NOT set overlap out-pulsing for any routes for SIP trunk. ie. "Digit before out-pulsing" should be blank.

[LoopyLou]

Think the only other thing you need to worry about is if your are using an MBG with your SIP trunks and upgrade to MBG 8. They changed a port used for SIP trunks and you will need the provider to change to the new port.

[ralph]

What's the new port number?   Is it now 5060 any longer?

Ralph

[martyn]

Got the same.

Although I always practice
b>  Do NOT set overlap out-pulsing for any routes for SIP trunk. ie. "Digit before out-pulsing" should be blank.

Same here. Australia actually gets told something first for once!

[LoopyLou]

Sorry what I meant was.

MBG 8.0 removes SIP support on UDP port 5064. Accordingly, the Legacy SIP Trunk Connector (which uses UDP port 5064) has been deleted from the SIP Options form.

Migration Tasks
1.Contact SIP provider to send to MBG on UDP port 5060 instead of UDP port 5064.
2.Change the port number from 5064 to 5060 for the MBG entry on the MCD Network Element form.
3.Change KPML Port from 5064 to 5060 on MCD SIP Peer Profile form