Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: lchung@candw.ky on September 30, 2024, 11:56:35 AM

Title: What is needed for a second sip trunk on MBG to a different carrier
Post by: lchung@candw.ky on September 30, 2024, 11:56:35 AM

Hi Guys,

I would like to add a second SIP trunk to my Mitel MBG.
What license info if needed and what configuration is needed.
I have tried to add the port configuration and sip configuration on the MBG but the system seem to try to establish a connection using the first carrier MBG ip.

Any help would be useful.
Thanks

Title: Re: What is needed for a second sip trunk on MBG to a different carrier
Post by: acejavelin on September 30, 2024, 09:10:28 PM

Did you build the network element in the 3300 and all the related SIP stuff? The MBG is the session border controller and an interface between "public and private" basically... The real configuration all happens in the MiVoice Business.

Title: Re: What is needed for a second sip trunk on MBG to a different carrier
Post by: lchung@candw.ky on October 01, 2024, 05:15:43 PM

Yes the network element is build and also all the SIP trunk stuff.
When I do a maintenance packet trace on the MBG, the trace is showing a setup from the first carrier mbg terminating ip going to the registrar of the second carrier, which will fail.
Is there a setting in the PBX that will tell the SIP trunk to use a specific ip address on call setup? 

Title: Re: What is needed for a second sip trunk on MBG to a different carrier
Post by: acejavelin on October 02, 2024, 10:04:40 AM

I guess I am confused... if you have a separate network element, communicating with a different external FQDN/IP then how is the invite being sent to the wrong carrier/IP? You essentially treat each SIP element as a separate trunk group, then access it via ARS and try a call, the invite should go to the MBG which then adjusts the IP's for the network translation (but shouldn't change it's destination) and forwards it off on the public interface to the destination carrier... 

Title: Re: What is needed for a second sip trunk on MBG to a different carrier
Post by: johnp on October 13, 2024, 04:20:41 PM

Think this may be clustered, I turn off all keep alives and never add any login info. Clustered keep alive will be done by both, both may contain the peers with differing addresses and function as designed. Like to limit only that going to each. Keep alives should be IMHO handled by the sip peer profile instead of the MBG setting.