Author Topic: SIP trunk seperation on 3300  (Read 1567 times)

Offline Apersons

  • Contributer
  • *
  • Posts: 14
  • Country: us
  • Karma: +0/-0
    • View Profile
SIP trunk seperation on 3300
« on: August 02, 2019, 01:14:15 PM »
Current system has a PRI to a t1/e1 card providing trunks. my customer wants to know if there is a way to have the same style setup on their new 3300 but with SIP trunks. They don't want to run the trunks through the same NIC as the phones. I don't think this is possible, but what's the harm in asking?


Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2202
  • Country: us
  • Karma: +66/-0
    • View Profile
Re: SIP trunk seperation on 3300
« Reply #1 on: August 02, 2019, 06:53:36 PM »
You could use an Adtran 908e to convert the sip to PRI or use an MBG as a sip proxy. The MBG woykd require sip licenses as well on the MCD

Offline VinceWhirlwind

  • Hero Member
  • *****
  • Posts: 899
  • Country: au
  • Karma: +31/-0
    • View Profile
Re: SIP trunk seperation on 3300
« Reply #2 on: August 04, 2019, 08:29:05 PM »
SIP is IP-based, so it will use the Controller's LAN NIC and IP address. That's just how it's going to work.

Offline acejavelin

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4100
  • Country: us
  • Karma: +133/-0
  • High-tech, heavy metal redneck!
    • View Profile
    • Like what I do and wanna help out? Send me a donation!
Re: SIP trunk seperation on 3300
« Reply #3 on: August 05, 2019, 10:06:28 PM »
You could use an Adtran 908e to convert the sip to PRI or use an MBG as a sip proxy. The MBG woykd require sip licenses as well on the MCD
If you have an Adtran converting SIP to PRI, you don't need an MBG at all. The Adtran is it's own SBC.

Offline acejavelin

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4100
  • Country: us
  • Karma: +133/-0
  • High-tech, heavy metal redneck!
    • View Profile
    • Like what I do and wanna help out? Send me a donation!
Re: SIP trunk seperation on 3300
« Reply #4 on: August 05, 2019, 10:08:38 PM »
... They don't want to run the trunks through the same NIC as the phones...
Why? This makes no sense at all, it is literally how it is designed to work.

In fact, this would cut down on traffic load through the Mitel controller... Right now all calls in or out of the system have to go to the controller, then be transcoded from IP to TDM and sent to the PSTN via the PRI. WIth SIP trunking, assuming you don't have a call recording server or something like that, the audio goes directly from the handset to the MBG (or other SBC) and only control signals go though the controller in most cases. It is literally easier for the system and reduced IP traffic to the controller when using SIP trunks, in most cases.
« Last Edit: August 05, 2019, 10:12:27 PM by acejavelin »

Offline billbry66

  • Full Member
  • ***
  • Posts: 93
  • Karma: +3/-0
    • View Profile
Re: SIP trunk seperation on 3300
« Reply #5 on: August 08, 2019, 06:40:32 AM »
tell them that only signalling will be via the LAN port of the pabx
the RTP( voice ) will be direct from trunk entry point to handsets
- only time RTP would go via pabx is if its hitting something TDm ( analog phone , moh or a TDM trunk)

Offline Apersons

  • Contributer
  • *
  • Posts: 14
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: SIP trunk seperation on 3300
« Reply #6 on: November 12, 2019, 02:45:52 PM »
For anyone who comes across this post,

We ended up adding a dedicated MBG for the outside SIP connection. Had to program the IP's on the MBG to look at the local IP addresses while the SIP traffic from the 3300 was pointed at the public IP set by the carrier. Set the MBG to server- gateway mode and it all work fine. 


 

Sitemap 1 2 3 4 5 6 7 8 9 10