john3voltas
Technical User
Hello,
== TLDR ==
Roughly half of the calls on this customer PBX are routing via VCM and the other half routing via direct media path for no apparent reason.
== Now some more details ==
One of these days, while looking at SSA, we detected that most calls were being routed via the VCM. Which seemed odd, because all trunks and extensions have "allow direct media path" enabled.
Giving it a closer look, we detected that even internal calls were being transcoded by the VCM/Jayde. Then we decided giving it an even closer look, and SSA does indeed report direct media path calls too.
So, it started looking a bit like 50/50, half using VCM and another half going DMP.
Running some quick tests with a couple of extensions we noticed that this happens not only with external calls (coming through SIP trunks) but also with internal calls too.
A couple of internal extensions, connected to the same LAN switch, on the same VLAN, thus on the same subnet, roughly half the calls between those 2 extensions will route via DMP and the other half through VCM.
Bear in mind this happens not only with these 2 extensions. This is a system-wide issue.
It is not the voice compression resources that we're worried about. It's the bandwidth. These 2 sites have 600 extensions on the IP500v2 side and they are all registering to the other site and RTP traffic is also routed via IPO server on the other site.
A few more details about the system.
Customer has 2 sites with a virtual SE R11.1.2 on one of the sites, an IP500v2 on the other site, a couple of SIP Trunks on each site and a mix of H.323/SIP Avaya endpoints, all registered against the SE server. Most endpoints are 1608's, 9620's and J139's and they are (unevenly) divided between both sites.
LAN switching is provided by Aruba 6000 series and Firewalling by Fortinet FG60, on both sites.
Any idea why this would be behaving like this?
Thanks in advance.
Cheers
== TLDR ==
Roughly half of the calls on this customer PBX are routing via VCM and the other half routing via direct media path for no apparent reason.
== Now some more details ==
One of these days, while looking at SSA, we detected that most calls were being routed via the VCM. Which seemed odd, because all trunks and extensions have "allow direct media path" enabled.
Giving it a closer look, we detected that even internal calls were being transcoded by the VCM/Jayde. Then we decided giving it an even closer look, and SSA does indeed report direct media path calls too.
So, it started looking a bit like 50/50, half using VCM and another half going DMP.
Running some quick tests with a couple of extensions we noticed that this happens not only with external calls (coming through SIP trunks) but also with internal calls too.
A couple of internal extensions, connected to the same LAN switch, on the same VLAN, thus on the same subnet, roughly half the calls between those 2 extensions will route via DMP and the other half through VCM.
Bear in mind this happens not only with these 2 extensions. This is a system-wide issue.
It is not the voice compression resources that we're worried about. It's the bandwidth. These 2 sites have 600 extensions on the IP500v2 side and they are all registering to the other site and RTP traffic is also routed via IPO server on the other site.
A few more details about the system.
Customer has 2 sites with a virtual SE R11.1.2 on one of the sites, an IP500v2 on the other site, a couple of SIP Trunks on each site and a mix of H.323/SIP Avaya endpoints, all registered against the SE server. Most endpoints are 1608's, 9620's and J139's and they are (unevenly) divided between both sites.
LAN switching is provided by Aruba 6000 series and Firewalling by Fortinet FG60, on both sites.
Any idea why this would be behaving like this?
Thanks in advance.
Cheers