MBG 7.0.7.0 and SIP Trunk to 3300

[danramirez]

Hi,

We currently have 2 SIP trunks (Skype) to our 3300 (4.1 SP1). SIP port UDP 5060 is now forwarded to the 3300 using a Fortigate F/Wall. SIP Trunks work excellent!!

Also, we have a MBG recently upgraded to 7.0.7.0 that is connected to the DMZ Port of the firewall. All ports 6801, 6802, etc. are forwarded from the WAN Interface to the DMZ according to MBG Eng. Guidelines. Teleworker SETs are also working fine, those can even talk to the SIP Trunk with no problem.

Now, we want to move those SIP trunks to the MBG (Already have SIP Trunk Licenses on the MBG) and Use the MBG as a SIP Proxy for the 3300.

Have any of you done this before with the latest MBG version?

Here is what we plan to do, let us know if we are missing any step:

-Forward UDP 5060 to MBG on DMZ Port
-Program MBG as an Outboud Proxy on the 3300 (Network Element Assignment)
-Select MBG Proxy in the SIP Peer
-Complete SIP Trinking params. (Services) on MBG

Regards,

Daniel

 

[danramirez]

Guys,

I moved the Trunks to the MBG and did the programming as described before.

Almost everything is working. Minet Teleworker sets OK, Sip Trunks OK, Teleworkers using the SIP Trunk OK, Audio OK.

This is what doesn't work: SIP Users (i.e. Xlight) register to the 3300 through the MBG, but we get NO audio. It looks like this is something to do with the programming on the MBG side for the SIP device, or the sip device capabilities on the 3300.

Any comments that may help?

Regards,

Daniel

 

[bobcheese]

I think there is somewhere in the MBG setup where you enable different protocols. I think by default only encrypted MiNET is enanbled. I'm just shooting from the hip here, will try to connect to one to check....

 

[danramirez]

bobcheese,

I just don't understand what's happening here. Everything works except the SIP users.

Remember that this configuration has got the MBG on the DMZ porT.

Question:

1. Should I select My MBG as proxy for the "sip device capabilities" on the 3300?

Regards,

Daniel

 

[bobcheese]

Not sure, if you issue the maintenance command 'SIP registrar contacts all' where does it show the registration IP address? MBG IP or far end IP?

 

[danramirez]

Bob, this is what it shows:

Registrar Entry(s)
--------------------
33:0x625 (0x10b76fe8) State[IN SERVICE:Completed] CEID[14:0] Accepting reg Agent:X-Lite release 1100l stamp 47546 Addr:sip:3588@10.0.120.10
Contact1: sip:dead59d36e83@88.26.229.238:5060
Time Left:824 Expires:900 Priority:0 Port:5060 Transport:1

10.0.120.10 is the ICP, 88.26.229.238 is Public Address that the MBG uses to go to the outside world (Firewall WAN Port). Remember the MBG is at the DMZ port of the firewall and the MBG IP is 10.0.116.2.

 

[danramirez]

two things...

Do any of you can help me answering these two questions:

1. After issuing the command SIP REGISTRAR CONTACTS ALL, I get the following:

Registrar Entry(s)
--------------------
9:0x12b6 (0x325d3a88) State[IN SERVICE:Completed] CEID[0:0] Accepting reg Agent:X-Lite release 1100l stamp 47546 Addr:sip:8585@10.1.120.101
Contact1: sip:dead72788d39@88.26.229.238:5060
Time Left:496 Expires:900 Priority:0 Port:5060 Transport:1

Why does it say "dead727..."? What do they mean with the word dead?

2. After issuing the command SIP REGISTRAR CONFIG, I get:

Registrar Configuration
-----------------------
Domain: 10.1.120.101 IP Address 10.1.120.101
Allow Third Party Registrations: no
Default Expiry Duration: 3600 seconds
Maximum Configurable Expiry Duration: 7200 seconds


Why doesn't this allow third party registrations? Where can I send that to yes? Will this make any efect on the audio problem that I having with UA traying to register from outside?

Reagards,

Daniel

 

[danramirez]

Boobcheese,

It all works now:

Minet Phones
SIP Trunks
SIP Users

Audio is available both ways between any combination, Minet phones to SIP trunks, SIP Users to SIP Trunks etc etc etc.

All the problem was at the Firewall. I was using Fortigate60B with an old version of Firmware. So before calling Mitel to open a ticket I wanted to give it a try by upgrading the Firewall to the latest f/ware.

I also disabled any kind of SIP Session Helper at the firwall and let the MBG to handle SIP. It all works!!

I will take a couple of screen shots of the programming at the F/wall and at the MBG and post it here for future ref.

Thanks for you ideas, regards,

Daniel

 

[cmcternan]

Daniel,

Did you ever get around to posting screen-shots of the MBG config?

We are trying to configure some SIP(skype) trunks on our MBG (7.0.7.0) and I seem to be running into a brick wall.

I have managed to configure the trunks on the 3300 (4.2) but am not sure how to go about configuring them on the MBG.

The Mitel Skype setup guide just says to use the MBG as a SIP Proxy, but there is no guidance on how to configure the MBG for this.

Is there any online documentation on how to configure trunks via the MBG? Or does anyone have any tips?

Cheers,

Conor

 

[danramirez]

Conor,

Let me get some screen shots for you of the programming for the MBG.

Give me a couple of minutes and I'll post the link

Question: Do you have your MBG in the DMZ port of your firewall?

I have it running with no problems.

Regards,

Daniel

 

[danramirez]

Conor, let me know if you need anything else.

here's the link:

http://www.yousendit.com/download/T2dkcHBOQ1JwaFMwYjhUQw

when making changes to the programming, allow a couple of minutes for the 3300 to register with skype service, it's not that fast...

let me know if you require screen shots of what I program in my f/wall. (Fortinet).

Regards,

Daniel

 

[danramirez]

guys,

Here is what I programmed on my firewall:

https://rcpt.yousendit.com/1279434664/82e27620bcab93277a0f42d24d81885f

Regards,

Daniel