Mitel Forums - The Unofficial Source
Mitel Forums => Mitel Software Applications => Topic started by: t2k on October 25, 2016, 09:13:26 AM
-
Hi All,
I have an MBG with teleworkers and SIP trunks connecting through to a Mitel 5000 v6. All works fine apart from withheld calls on the SIP trunks are not connecting.
I can make a call through to a teleworker on the MBG via a SIP trunk on the MBG and the call works fine, do the exact same call with 141 in front and the call doesn't connect.
I am new to the MBG and I expect this is where the problem lies, I have set up a rule on the MBG which is - Request URI - * - Primary - Mitel 5000
Any help would be greatly appreciated.
Thanks
-
Mitel product support should be able to help. The first thing they'll ask for is a network trace.
If this is a UDP trunk, can you provide a pcap file to look at? Also, what version of MBG is this?
-
Hi Navarre,
Thanks for the reply. I'm Mitel 5000 trained but not MBG so wasn't sure if Mitel support would help, no harm in creating a support call I guess.
I have a wireshark capture from the SIP provider but not sure how to upload it! The MBG is at 9.3.0.17
-
I have a wireshark capture from the SIP provider but not sure how to upload it! The MBG is at 9.3.0.17
You can use any file sharing service.
-
https://dl.dropboxusercontent.com/u/21226498/Weldmar/out1.pcap (https://dl.dropboxusercontent.com/u/21226498/Weldmar/out1.pcap)
Hi Navarre,
Attached should be a working call then the same call with 141 infront and the call fails
-
Hi,
I don't think the 5000 likes the anonymous.invalid and is rejecting it.
Looking at the source IP are these Gamma SIP Trunks?
On your 5000 SIP Peer under Alternate IP/FQDN enter either the internal IP of the MBG or anonymous.invalid
What happens if you test again?
-
Thanks Markyb73,
Adding the MBG address sorted it, much appreciated.
Thanks
T2k