Remote Branch 1way hearing prob and another prob

[Phoneguy15]

I am installing IP phones at a remote branch for a customer back to an S8300/G700 at the host site across the WAN with a MultiTech MultiVoIP unit for Survivability.

I have a problem with station to station calling, when I call from the remote branch to the host site across the WAN, I can hear ringing but, when they answer I cannot hear them. They can hear me fine.
Any ideas?

2nd problem;
when I test the survivablity of the MultiVoIP by taking down the WAN link, the MultiVoIP takes control of the phones and trunks fine, but when I restore the link and the phones reregister with the 8300 the trunk group and the signaling group are going (or staying) "out of service". I have tried busying out and restoring the signaling group and the trunk group, but that does not help.
The only way , so far, that I have been able to get it back up is to remove the signaling group and rebuild it.

One more thing that I have checked is that when this is down, I can ping the MultiVoIP from a local machine, but when I "go shell" from the Definity command line and ping the address I get "destination Host unreachable". I know that it is not the link though because my phones have reregistered to the 8300 and I can call between stations locally.

TIA,
Todd

 

[syntax18]

Did you check if they are full duplex

 

[Phoneguy15]

I didn't see that option on the station screen.

 

[ph0neguy]

In answer to your first question about the talk path issue, if you display events and in the category put denial and at the bottom of the screen put in the station number that you get that condition with and look for anything that says no voip resource available. You should try to ping the ip phone from the media processor tn2302. If that works ok I'd look at your network region configuration because if you have IP connectivity the Avaya pbx software should be able to give that phone the RTP packets it so desperately needs.

 

[avayaconsultant]

A quick question to help with your problems. It may be off, but do you have other IP phones operating properly on the network? If not, do you have your MedPro board configured properly? You should have it and the switch port it is connected to set to 100 Full Duplex. No MedPro = No audio. You will hear the rings but get no audio.

Next, do you have multiple C-Lan boards? If you have multiple c-lan boards and are not using network regions, make sure the gateways on the C-LAN boards can be reached by the remote office.

Next, please make sure you have the latest firmware updates on both your C-LAN and MedPro boards. Always ensure that when you upgrade the firmware that you are using the proper firmware for your boards hardware rev. (This could help prevent the issue with losing the IP trunking and removing the sig group... I am speaking from experience)

Always doublecheck the IP Address' of the phones and the Multitech device. Double check to make sure they are all able to talk back and forth.

If you are using a Cisco router (just in case) there are a couple of changes that nee dto be made there as well in an IP setting for Avaya to work properly.

Finally, are you definitely using option 176 on the DHCP server? This is vital to the Multitech working properly as far as the IP phones are concerned. Which MT Multivoip are you setting up here? I just finished full deployment and saw many of the issues you are having here.

 

[PBXTech]

Isn't one way talk paths indicative of an issue on older firmware on the MedPro boards?

 

[avayaconsultant]

Yes it was an issue with an older firmware as well as not having a MedPro at all in the system or the MedPro could be misconfigured.

 

[Phoneguy15]

Ok, here is what I have found so far,
The 1 way talk path only occurs when I have direct IP to IP audio connections turned on in the station admin (page 2).
If I turn IP to IP off I can only make/receive one call per station.
This is an S8300 and G700 config, so there is no CLAN or MedPro boards to deal with. I have confered with Avaya and they said to upgrade the firmware on the internal VOIP module and the MGP. I have done so.
We are using Cisco routers between the 2 branches, so I would be interested to know what changes need to be made in them for Avaya's IP stuff to work.
Today I will be going to another branch that we will be deploying the same setup to see if we can have 2 way talk path's across the WAN link there.

The issue with the Multitech I believe is resolved mysteriously. It started working perfectly after Multitech engineers dialed in and looked at the config and said that everything looked fine. Hmmmnnn? (it is an MVP-810-AV)
I think that the trunk group and signalling group problem was because the Multitech was not releasing the trunks back to the S8300 when the link would come back up.

Thanks guys,
Todd

 

[Phoneguy15]

oh yeah,
The IP addresses are fine on the phones & Multitech because I am able to place calls from the phones @ that branch through the MultiVoIP to the PSTN. I can also receive calls from the PSTN through the MVOIP to the phones.
I am using option 176 on the DHCP server.
The fail over when the WAN link goes works fine (from the 8300 to the MVOIP gatekeeper)
thanks again,
Todd

 

[avayaconsultant]

How are your firmware revs?

Chris Shelton
Innovative Technology Solutions

http://www.inntechsolutions.net

 

[Phoneguy15]

well, I found it.
Apparently when the host site was installed the router address that was programmed into the phones there was not the correct one.
I changed it to the correct address and it works great.
It is amazing what happens when you get all the stars and planets aligned in the correct order....

Thanks for all the input,
Todd