Direct Media Path issue 1

[Onorio]

Hi,
I have been reading some other topics about the DMP, but I don't know if it fixes to our issue.
Basically I have the IPO in one center and other center connected by VPN. Ip addresses from both centers are in different subnets but both can see each other. A firewall is in between both sites. The firewall allow to connect from the VPN to the Control Unit (but it is denied to the rest of the net).
So when a softphone from the center of the VPN make an outbound call everything works fine because the Control Unit is involved, but when make a call to another softphone of the other center the phone rings but no audio or RTP messages.
So it is working as expected because the firewall only allows to connect from the VPN softphone (Avaya Communicator) to the control unit but no to the rest of the net. So it looks like calls between sip users the IPO is only working to make the signaling call but then the audio go straight between Avaya Communicator so it is ban by the firewall.
Is there a way to force to make the call between users using the IPO as audio intermediary.
I assume DMP only affect to SIP/H323 Trunks, which I think is not involved in this situation.
I will appreciate any comment. Thanks.

 

[cg11]

Sounds like ports are being blocked somewhere. The general rule is to turn off DMP when deploying phones on another (remote) subnet. Try turning DMP off for the remote phones, reboot the remote phone and post results back here.

 

[Onorio]

But they are not SIP or H323 phones where I can untick the DMP, it is Office Workers licenses using Avaya Communicator as softphone, so I don't find any DMP related with those users.
The only place I see the DMP is in the H323 trunk that connect Primary Server with IPO500V2 where are connected digital phones. By the way the calls between Avaya Communicators from the VPN to the digital phones work ok with audio, the issue is only calls between Avaya Communicators in both sites.

 

[cg11]

Okay, DMP is normally under "extensions", not users. Check there. There should be a checkbox on the right side.

 

[Onorio]

I am afraid, there is no DMP in users or at least I didn't find it. Also there isn't for the full system, I just found it in Lines and SIP/H323 Extensions.

 

[cg11]

DMP should be under "Extensions" (at least to H.323 phones).

 

[Onorio]

Yes, but Avaya Communicator doesn't need extension, it is enough with the user pointing it is a Power User. So there is no extension for each Avaya Communicator user.

 

[cg11]

okay, then check that no SIP ports are being blocked by your firewall or VPN. A blocked port will sometimes show up as one-way talkpath.

 

[Onorio]

Furthermore, I just tested to create 2 SIP extensions unticking the DMP and assigning 2 base extensions of 2 Power users (one local and another in the VPN site) and it doesn't solve the problem, still no audio, so it convince me the Power Users doesn't need an extension.
Yes, for sure the Firewall is blocking the communication between site 1 and site 2 because only allows that traffic when it is against the IPO ip address, but not when it is straight between ips of the PCs with the softphonees.
So the question was if I can deny the DMP to the Avaya Communicators in order to avoid changing the Firewall.
Many thanks for all your answers.

 

[janni78]

Well, guess someone at Avaya didn't think this one through =)

If you create a SIP extension I think it will use their settings it instead of creating a virtual extension.
Although I would allow the 2 nets to talk RTP to each other since I prefer using DMP very possible.

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

 

[Onorio]

Yes, I agree with you, I prefer DMP as much as possible, but in this case the firewall is managed by an external company which is very very slow for any new setup, so I was trying to avoid it.
I also believe Avaya Communicator is not well designed by Avaya, the same you can not login as an agent as the digital phones allow. For me it is very disappointing design.
From my point of view although you create a SIP extension it is now used by the Power User.

 

[janni78]

Just tested, changing extension settings doesn't do anything with Avaya Communicator.
Also found a support post saying it isn't possible to change DMP.

It works with other SIP devices as intended, tested with Equinox and One-X Communicator, the later uses an Avaya Endpoint.

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

 

[Onorio]

Thanks you for your comment janni78. It is a pity it can't be changed, again Avaya Communicator is the forgotten part.