Mitel Forums - The Unofficial Source

Mitel Forums => Mitel Software Applications => Topic started by: brogerson on June 10, 2019, 08:36:11 AM

Title: One Way Audio on Teleworker
Post by: brogerson on June 10, 2019, 08:36:11 AM

I have a teleworker set connected to a MBG that is in the DMZ.  I have a PBX and MBG SRC for call recording on the Internal network.

If I login to my Teleworker MBG and configure my set to register with the SRC I have no problems with one way audio. If I point my set to the PBX audio is not getting out to the teleworker set depending on the type of call.   If I call an extension on the PBX I have two way audio,  If I call the embedded mail or call out on the SIP Trunk I have one way audio.

I believe the firewall is configured correctly because I have two way audio if my set is registered to the SRC or if I call an extension.

Title: Re: One Way Audio on Teleworker
Post by: Tech Electronics on June 10, 2019, 01:48:04 PM

brogerson,

Are you saying that if you point to the MBG the phone works as expected, but if you bypass the MBG and point it to the PBX it doesn't?

Why are you not pointing to the MBG for all your Teleworker phones?

Thanks,

TE

Title: Re: One Way Audio on Teleworker
Post by: Dogbreath on June 11, 2019, 05:18:05 AM

Quote from: brogerson on June 10, 2019, 08:36:11 AM

If I login to my Teleworker MBG and configure my set to register with the SRC I have no problems with one way audio.
If I point my set to the PBX audio is not getting out to the teleworker set depending on the type of call.   

To clarify "point my set to the PBX", do you mean from the configuration of the handset itself, or by choosing the "Configured ICP" for the extension in MBG?

Quote from: brogerson on June 10, 2019, 08:36:11 AM

If I call an extension on the PBX I have two way audio,  If I call the embedded mail or call out on the SIP Trunk I have one way audio.

Are you using MBG SIP proxy for the SIP trunk? What type of MiVB is it? Bear in mind with vMiVB, the embedded voicemail media stream won't be coming from the IP where the ESM web interface lives, it will be coming from the MSL instance's IP. If you're using NuPoint then that's probably [don't know, never used it] yet another IP that will need to be allowed to talk to the MBG.

If everything works when configuring handsets to use the SRC as their "ICP" then I would be tempted to just leave it at that. TAP licenses are only used when calls are recorded.