SIP trunks between MCD's

[StardataMitel]

Hi all,

I'm chasing information on how to setup SIP trunks between an MCD and vMCD.
Not sure if this is even possible.

The vMCD is a standalone system and until the business's SIP provider comes online we need to use a 3300 as a gateway.
Any knowledge on this would be greatly appreciated.

Cheers

 

[Supernova99]

Question:
Do both systems have IP trunking? if so then this is the preferred and better option.

SIP trunks between systems is fairly easy to setup, and works well you just need to bear in mind that SIP trunking is licenced per call (session) so you need to ensure you have enough sessions available so that you don't create a bottleneck and get busy back.

Briefly:
Just create a Network element on each system and set the type to 'Other' enter IP address
Create a SIP Peer Profile on each system and use the network element previously created and select max sessions that you want. (I think you can pretty much leave the rest of the settings at default)
Program the ARS to route calls between systems.

For outgoing calls
From vMCD to gateway - 9xxx (remember to send the 9 or trunk access digit)

For incoming calls
From Gateway to vMCD - DDI leading digits (e.g. if extension numbers start with 2 then create ARS 2xxx)



Share what you know - Learn what you don't

 

[StardataMitel]

Thanks Supernova,

Unfortunately the vMCD is licensed as a standalone and will not let me put an ip for the far-end system in the ICP/PBX Networking form.

Thank you for the brief setup instructions, most of them i had worked out for myself.
The trunks still aren't registering successfully though.
I have a feeling that this may be to do the User name and password authentication for the trunks.
Do I use the ESM Login credentials from the other system?
Can i leave them blank?

 

[Supernova99]

It is probably the other way around, where the MCD does not have an enterprise licence and the vMCD does.
Yes you can leave the credentials blank as they are 'private' normally username and password is required on public internet SIP links.
Also did you set the SIP Peer specific info in the Network Element form for the SIP ports? by default it is set to 0 make sure they are set as port 5060



Share what you know - Learn what you don't