Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SIP Networking between 2 remote Mitel 3300's using Public Network 2

Status
Not open for further replies.

kwbMitel

Technical User
Oct 11, 2005
11,504
CA
I'm looking to see if anyone has tried setting up SIP trunking between 3300 systems over the Public Network

I did it on an internal LAN maybe 10 years ago using ARS and SIP trunking but I've never involved MBG's and the Internet.

If anyone has done it (or Tried), I'd be interested in hearing what you have to say about it even if that comment is don't bother.

All virtual machines, Rel 8.0 on one site, rel 9.0 on the other.

This is worth far more than a Star if I can get it working. I'll see what we can work out if it gets there.


**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.
 
Hello KWB, I don’t see a reason why this should not work.

I am more than happy to help with this experiment. Tomorrow morning I will do some testing between my lab environment and a friend’s MiVB/MBG arrangement. I will share results.

I am in Europe, so by the time you wake up you will have my feedback. Are you in Canada?

Cheers,

Daniel

 
Edmonton Ab Canada -7 GMT 13:03 pm at time of this post

The more I think about this, the more feasible it seems. Could be very useful.

**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.
 
Evironmet A:

MiVB 8 (sits in the LAN)
MBG on the DMZ port of Fortigate firewall (Ports UDP 5060, and the range 20000-31000 are forwarded from Public IP address to local IP of MBG)
WAN of the firewall connected to Internet with Fixed IP asddress A

Environment B:

MiVB 8 (sits in the LAN)
MBG on the DMZ port of Fortigate firewall (Ports UDP 5060, and the range 20000-31000 are forwarded from Public IP address to local IP of MBG)
WAN of the firewall connected to Internet with Fixed IP asddress B

Configuration on both sites is equivalent, I will only describe one:

1. On the MBG create a new SIP Trunk and point it to the other-end Public IP Address, I also enabled accept traffic from any port, and added a rule that * goes to the local ICP.

2. On the MiVB, I added a new network element:
2.1. FQDN or IP Address: Remote Public IP address
2.2. SIP Peer Transport UDP
2.3. SIP Peer Port 5060
all the rest leave it as default

3. Create a new network element for your local MBG

4. Create a new SIP Peer:
4.1. Refer it to the network element you just created in 2.
4.2. Address type should be IP Address
4.3. Select your MBG as your outbound proxy
4.5. Select a trunk service number and maximun calls to whatever values you feel confortable. Of course your Class of service should has Public Netwiork access via DPNSS and in this case I absorb 0 digits.

that's it, configure your ARS and call an extension on the other end. Signaling and audio was great.

Note:
-I did not require to configure anything is SIP Peer Profile assignment by incoming DID
-I don't feel comfortable with the security of this method, I would add user name and passwords and most probably Registrar parameters would be required in the Netwiork Elements
-I would use FQDN instead of Public IP in the Network element and involve DNS (Publics and locals)
-I didn't use compression but I guess if we enable a different zone, 729 will be used.

If you'd like to do testings between your lab and mine please let me know.

Cheers,

Daniel


 
good one

If I never did anything I'd never done before , I'd never do anything.....

 
By the way, one of the things we should try out is configuring the setup on one end and try to bring the trunk up from a foreigner IP address. If this is allowed then we definitely have to think in bringing security to the trunk.
cheers,
daniel


 
I gave it a try but it didn't work.

I suspect the firewall for one site is locked down for port 5060 to specific IP's

I will try this again later, giving the star regardless

**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top