I have kind of a weird issue and I will be the first to admit I simply do not have a lot of hands on experience with Server Edition. Issue is a user has one way audio on Avaya communicator but only when dialing out over the PRI. User is on the Server and the PRI is located on the IP 500 V2 expansion. I noted they had an error in system status about a codec mismatch and that direct media path may not work. I turned off direct media path on the SCN lines and it does work like this (so its a routing issue). I removed the codec from the lines that was mismatched which resolved the error but if I turn direct media path back on it still does not work.
If the user calls any user, on the server or the IP 500 V2, it works just fine with direct media path enabled for the users extension. It only fails when using the SCN to get to PRI and then goes outside. IP phones work with same connection. If the computer with communicator is moved to the voice VLAN it works (again pointing to a routing issue). It appears the routing between the VLANs work as you can connect to the server edition even on the data VLAN. I am told that there is no firewall between the server edition and IP 500 V2 just a VPN connection. If you connect with a software VPN with communicator it also works.
I just am at a loss why calling an extension on the IP 500 V2 is fine but using the PRI on the IP 500 V2 is not fine. Again, obviously a routing issue somewhere, most likely between the server edition and the IP 500 V2, I just can't seem to put my finger on it. The customer is content right now with just not using direct media path but as we all know that is a bandaid and is not the end solution.
I did also note that the Server edition is on ULAW and the IP 500 V2 is on ALAW (they are in different countries with a VPN between them). I would imagine this is ok but figured Id throw it out there.
The truth is just an excuse for lack of imagination.
If the user calls any user, on the server or the IP 500 V2, it works just fine with direct media path enabled for the users extension. It only fails when using the SCN to get to PRI and then goes outside. IP phones work with same connection. If the computer with communicator is moved to the voice VLAN it works (again pointing to a routing issue). It appears the routing between the VLANs work as you can connect to the server edition even on the data VLAN. I am told that there is no firewall between the server edition and IP 500 V2 just a VPN connection. If you connect with a software VPN with communicator it also works.
I just am at a loss why calling an extension on the IP 500 V2 is fine but using the PRI on the IP 500 V2 is not fine. Again, obviously a routing issue somewhere, most likely between the server edition and the IP 500 V2, I just can't seem to put my finger on it. The customer is content right now with just not using direct media path but as we all know that is a bandaid and is not the end solution.
I did also note that the Server edition is on ULAW and the IP 500 V2 is on ALAW (they are in different countries with a VPN between them). I would imagine this is ok but figured Id throw it out there.
The truth is just an excuse for lack of imagination.