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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Not your usual one way audio problem.

Status
Not open for further replies.

RDECIT

Technical User
Apr 28, 2009
376
GB
Background: MBG (Server Gateway) and MCD

We've been experiencing one way audio on the teleworker sets for some time, but it only happens when the teleworker rings certain sets at the headquaters. Most people would put this down to firewall rules. However we replaced one of the none working sets at the headquaters and it started working for that set. I havent spent anymore time fixing this.

Now today I've setup MCD to Exchange 2007 UM. Everything works apart from some sets when you try to enter your mailbox number or pin the key presses are not registering, the UM system then asks if your still there. I also tried the Exchange UM Auto Attendant, when I speak the name of a user on the system, the Exchange UM reports no name spoken.

The twist to this problem is that the sets that don't work with UM are the same sets that have problems with Teleworker. I've checked the COS of both groups of working and none working sets, they are all the same.
 
Probably the usual suspects.

Biggest clue is if the 1 way audio is at the TW set. (can be heard but does not hear office set)

The main reason for this is the packets from the office set are being directed to the internet thru the data connection and not thru the TW server.

If the TW server is on the same network as the phones then try setting the GW for the phones to the TW.

If the TW server is on a separate network, make sure the gateway for the phones directs ALL internet traffic from the phones to the TW server.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Thanks for the response kwb, but as I mentioned in part two if we forget about the TW issue and concentrate on the Exchange UM, the exact same internal sets that have one way audio problems with TW, suffer one way audio with UM too and this is just a LAN call, we can hear the UM server but it can't hear us
 
Rob, can we clarify. You have sets that when called by teleworkers get one way audio or if these same sets call the Exchange voicemail, they get one way audio?
 
Also clarify which end gets the one way.

If the TW set hears the internal set then I will accept the Not Usual.

Otherwise you have a routing issue (even with the exchange experiencing the same issue) Probably the exchange is on a different network that the phones in question can not route to.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Probably a routing issue. To see if it's internal or external, take a look at the TW server. Keep in mind that when an internal set calls an external TW set, the internal set is told to stream to the TW server, the server then forwards the packets to the external TW set. If you don't see packets hitting the TW server from the internal set, then it's an internal routing issue as mentioned.

My guess is that if you re-replace that set that now works with the one that doesn't it will now work. It probably had some stale DHCP options/gateway address.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top