remote phones extn to extn audio issue 5

[MaximusBrian]

hey guys,

trying to figure this one out.

setup:
-ipo v9.1 r12 behind a asa 5520.
-9608g phones are being used by people from their home via ipsec vpn through the 9608g

testing:
for remote users, they can receive calls via ICR, dial out, get calls via VMPro with no issue.

summamry:
currently almost everything is working in office and at home except the audio for extension to extension dialing.
while working remotely via vpn, when you dial an extn, the call connects but no audio.

 

[icet500]

Disable “allow direct media “ for these extensions.

 

[janni78]

You either need to allow traffic between the VPN connections or do as icet500 said.

"Trying is the first step to failure..." - Homer

 

[MaximusBrian]

@icet500, direct media has been disabled from the inital sip trunk configuration

@janni78, on the asa, intra and inner communications are already enabled.

on another note from this thread,

https://www.tek-tips.com/viewthread.cfm?qid=1802114

derfloh (TechnicalUser)10 Apr 20 17:04
This route doesn't matter.

If the VPN network is 192.168.199.(1-254) you have to create a new IP route:
Adress: 192.168.199.0
Mask: 255.255.255.0
Gateway: you local gateway
Interface: the IPO LAN interface that can reach the Gateway.

 

[kwing112000]

you have to disable direct Media on the IP extensions.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Vive Communications

 

[MaximusBrian]

@kwing112000 - thank you! that did the trick.

if anyone else runs into this issue:

go to extension -> select the h323 extension -> voip tab -> uncheck "allow direct media path

 

[icet500]

FYI, Extension to extension calls does not use sip trunk.

 

[gwebster]

Disabling direct media is just a workaround and can cause QoS issues due to extra transcoding as well as load on the IPO due to processing. As janni78 pointed out, your VPN is probably configured to not allow packets from one tunnel to flow to another tunnel. That is usually the default operation. If you enable tunnel-to-tunnel packets, then you can enable direct media.

 

[Travis Harper]

Disable Direct media on the remote extension. This only works on Layer 2 networks.

 

[janni78]

This only works on Layer 2 networks

This is incorrect.

There is no point in routing all voice traffic through the PBX, even less so if you start using SRTP since it puts a lot of load on the PBX to anchor a lot of encrypted calls.
I always try to use direct media, preferably no VCM resources should be used for connected calls.
Disabling direct media is the lazy solution when you (or the customer) don't wanna solve the actual issue in the network.

"Trying is the first step to failure..." - Homer

 

[icet500]

Totally agree,

 

[MaximusBrian]

@gwebster - i would like to have it work the way intended, thank you for pointing me in a direction to start.

question, is there certain ports to open for this? in the asa, it is setup for the traffic from the voicevpn group to access the ipo on the private subnet thus the phone being able to authenticate and request extension/password. you can make and receive calls, just not extension to extension. it will connect but silence.

as a note, most users are remote from home or wherever so they're 9608g's are vpn'd to the office.

@janni78 - understand what you're saying, i would like to learn/resolve the issue so it will be more efficient on the system and elsewhere.

 

[derfloh]

You just have to ensure that traffic from one VPN Client to the other VPN clients is allowed.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN