Author Topic: Sonicwall config for SIP trunk on MCD without MBG  (Read 2338 times)

Offline barry4900

  • Contributer
  • *
  • Posts: 10
  • Country: us
  • Karma: +0/-0
    • View Profile
Sonicwall config for SIP trunk on MCD without MBG
« on: June 16, 2016, 10:21:57 PM »
We are setting up a MiVoice Business 7.2 on a CX II controller.  We have a Fusion SIP trunk without an MBG proxy.  We are able to make and receive calls but there is no audio.  The firewall is a SonicWALL 2400.  Does anyone have any information on how to configure the firewall to pass RTP traffic to the phones after the call is up?

thanks

Barry


Offline x-man

  • Hero Member
  • *****
  • Posts: 1129
  • Country: gb
  • Karma: +25/-0
    • View Profile
Re: Sonicwall config for SIP trunk on MCD without MBG
« Reply #1 on: June 17, 2016, 06:26:27 AM »
First option is to turn SIP-alg off if you can find it on the Sonicwall.

Depending on the provider and the auth of the SIP depends on whether you then have to open some ports up.

Offline barry4900

  • Contributer
  • *
  • Posts: 10
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: Sonicwall config for SIP trunk on MCD without MBG
« Reply #2 on: June 17, 2016, 08:26:53 AM »
By enabling SIP Transformations under the VOIP settings on the Sonicwall, we have progressed from no audio to one-way audio.  The receive audio on the Mitel Superset is working but transmit audio is not.

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Sonicwall config for SIP trunk on MCD without MBG
« Reply #3 on: June 17, 2016, 08:27:51 AM »
Be sure that the firewall allows access to the entire voice network - not just the PBX.
Once the call is set up streaming goes directly to the end point.  The PBX does not proxy RTP.

Ralph

Offline barry4900

  • Contributer
  • *
  • Posts: 10
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: Sonicwall config for SIP trunk on MCD without MBG
« Reply #4 on: June 17, 2016, 11:36:18 AM »
After spending a couple of hours on the phone with Sonicwall and Mitel support engineers capturing packets and doing Wireshark traces, it turns out that the phone was bad.  All that had to be enabled on the firewall was Sip Transformations.

Thanks for the replies.

b


 

Sitemap 1 2 3 4 5 6 7 8 9 10