vMBG &VUCC SIP Trunk

[warlockcode]

Hi

I am trying to set up virtual MBG and virtual UCC with AAPT (Telco) SIP Trunks.
I have been given a private SIP line from AAPT to use and to route calls to together with a /30 subnet.
I have fortigate network firewall/router that does all my internal/external routing.

I was wondering if someone can assist me with any documentation that will help me achieve this.

Cheers

 

[AlphaMann]

First off go to MOL (Mitel Online) and lookup the Config Guide 13-4940-00255 as AAPT is a tested and certified provider. This will give you all the steps that AAPT and Mitel did to get the SIP trunks working.

Also I know on the Forte Gate I have had to make the following adjustments in the past, different SIP provider so it may not apply. I would try the Config Guide steps first and then adjust if you need to further:

PLEASE NOTE!!! I AM NOT A FORTIGATE EXPERT. I FIGURED THIS OUT BY TRIAL AND ERROR AND CANNOT PROVIDE FURTHER ASSISTANCE!

From the Fortigate CLI (logon to the web admin and you can click on the CLI console)

config system settings
set sip-helper disable
set sip-nat-trace disable
end

config system session-helper
show (look for the entry for SIP, mine was 13 on both systems)
delete 13
end

config voip profile
edit default
config sip
set rtp disable
end
end

config voip profile
edit strict
config sip
set rtp disable
end
end

quit

Restarted Fortigate (probably don’t have to but I did anyway)

PLEASE NOTE!!! I AM NOT A FORTIGATE EXPERT. I FIGURED THIS OUT BY TRIAL AND ERROR AND CANNOT PROVIDE FURTHER ASSISTANCE!

 

[warlockcode]

Thanks AlphaMann

Do you have this guide with you, can you share it here as an attachment and I can download.
I tried looking it up, but was not able to find it.

Much appreciated

 

[warlockcode]

I have managed to configure the vMBG and vUCC, works fine - local users and trunks.
However I am having an issue with the Teleworker phones. They boot up alright, but they drop again with error : "Contacting Server".
After sometime it will reboot and then does the same thing all over again.

To eliminate my firewall I have opened all the ports, still no change.

Teleworker is registring from this MBG -

Network profile Custom mode
Security profile Legacy mode
WAN IPs None
LAN IPs 192.168.27.10
Third IPs None
Set-side streaming addresses 203.XXX.XXX.XXX
Icp-side streaming addresses 192.168.27.10

Users are registered on vUCC -

Network profile Gateway mode
Security profile Legacy mode
WAN IPs 10.10.1.1
LAN IPs 192.168.27.2
Third IPs None
Set-side streaming addresses 10.10.1.1
Icp-side streaming addresses 192.168.27.2

Any help would be appreciated.

Thanks

 

[AlphaMann]

So you have no external IP on the MBG?
Are you using a DMZ or trying to NAT an address?

 

[warlockcode]

I have managed to stabilise my Teleworker test phone, I dont really know what I did.
But one thing I can remember was adding in the network for the vMBG into the vUCC's server.

Now with that settles, I was able to make a call out and audio both ways.

Calling in was a mission, still trying to find out what is causing the issue.
When I dial in, I can see the call terminating to the vMCD (VUCC) however it is not ringing my Teleworker phone.

Here's my scenario:

From the Internet (teleworker) I can call in through to the Fortigate, into the vMCD/vUCC/vMBG, through to the cisco router and out through to AAPT - Tested OK

From the external (cell phone) call comes through to AAPT to the Cisco router, through to the vMCD/vUCC/vMBG , and this is where it ends. - Packet gets dropped.

Can it be my firewall dropping the packets coming from the 10.10.1.x range?
Any fortigate expert out there??

Cheers

P.S. AlphaMann my external IP is the "Set-side streaming addresses 203.XXX.XXX.XXX" mapped via DNS to 192.168.27.10

 

[warlockcode]

MBG is showing this error
"MakeCall by DN 8*74 using monitor 18a74 to destination 874 failed. Reason: SXERR_FEATURE_NOT_ALLOWED