Logix

I have an Avaya S8720 at a central location. (Cm4.0). This is configured on network region 1.
I have a G350 gateway hanging of it . This is configured on Network region 2

Is there a way that inter region calls originating from NR2 to NR1 can use the Medpro resources on NR1 (The s8720 site) rather than allocating a local NR2 resource for the call.

The scenario is as follows:

Both sites are connected to our WAN and have separate IP address ranges.
The S8720 central location has an IP trunk connected into our WAN. Our Wan provider acts as an Off-Net trunk/route .

When a call originates from the G350 Gateway through the Central site and out over the IP trunk, the G350 Voip module IP address is advertised as the Medpro resource.
This is a native IP address to that particular site (The gateway site). The WAN provider have a route in their network to this IP address range directly. Therefore Media packets are routed directly to the gateway location - Not via the Central location.
The result is that the call set up and tear down is successful but there is no audio.
I have never ran into this type of bearer/signal separation before so not sure if it should work.

In order to resolve the issue I have suggested we look to use Medpro resources allocated at the central site. This would mean that in all cases the advertised IP address would be that of the central site, so all audio packets would routed correctly. I just don’t know if this is possible.



Any ideas?

Thanks In advance

martinyoung

I will give the old answer because I am not current on the latest CM and matters may have changed. In older loads CLANs can be used in more than one network region but you needed a MedPro in each network region that requires that resource.

__________________
Marty
Retired Avaya DSIC tech

PBXtech.info

 

stubborne

what do you have at the 350 gateway site - ip phones? Sounds like you have shuffling enabled. If the route to the IP trunk exists on the 8720 site, then if shuffling is off, you should have an audio path like this 350 -> 8720 (med) -> ip trunk endpt..

Also, you may be able to solve this in your network. Sounds like you could be possibly blocking the rtp (audio) pkts in your network between the ip trunk endpt and your g350. Check in NR 2 for the settings and, depending on what type of QoS you have on your network (whether you use IP Prec or diffserv value), ensure those pkts can traverse the network.

__________________
Stu

Logix

Thanks Guys -

I have considered the fact that perhaps I need a medpro at the S8720 Central location in NR 2 . But my question would then be how do I select that Medpro resource in prefference of the NR2 medpro resource at the G350 Gateway?

I do have IP phones at the gateway , so the Voip module (and Medpro resources) is required .

Shuffling is turned off . I use a Medpro resource on NR 2.
When on - I shuffle to the medpro of the originating NR 2.

This appears to be the cause of my woes.

I am currently looking at how to get the WAN to route packets to this particular IP address (The IP address of the gateway Voip module in NR 2) via the central location. I do think this will also resolve the problem.

I would just have thought that there was an "Easy way" (In Avaya talk these two words are rarely used together) to select which Medpro pool should be used of inter site communication. The resources in NR1 or the resources in NR2. (Non dependant of call origination)

Thanks for your input

sparkee

you can use the ip map to assign the handsets to NR1 therefore using the medpro in NR1

Logix

Thanks -

I asume this will work - But I also assume that any call then made from said handset will always uses a Medpro resource in NR1. (Even for Inter gateway calls) which I would like to remain using NR2 resources.

Or - What about I do this : Map the phones to NR 1 (as suggested) then enable shuffling on NR 1 - This would then release the NR 1 resources for inter gateway calls -

I will try it.

PBXtech.info