Connecting to UC Module through the network 1

Did you adhere to the following:

The IP500 V2 system has two physical LAN interfaces: LAN1 and LAN2. The ports labeled LAN and WAN respectively. The
Unified Communications Module is physically connected to the LAN1 network of the system and needs to have an address
on that subnet.

· User and Administration IP Addresses
User and administrator access to the Unified Communications Module and the applications hosted by the module
use the following addresses.

· Unified Communications Module
A newly installed Unified Communications Module uses the IP Office system's LAN1 IP address for browser
access to the module's initial configuration menu. During that initial configuration, an IP address for future
access to the Unified Communications Module is set.

· one-X Portal for IP Office
The one-X Portal for IP Office service running on the Unified Communications Module is accessed using the
module's IP address or DNS name suffixed with :8080 as the port number.

· Voicemail Pro
The voicemail server service running on the Unified Communications Module is accessed by the Voicemail Pro
client using the module's IP address.

-SD-

Working through this exact same fault with Distributor on a site right now. New install.

Is there an Avaya switch involved with VLanning?

You may also find you have difficulty getting your ICR to hit a VM module and obvoiusly browsing to the UC110s GUI interfaceon port 7070.
If this happens, try and forward your ICR to a voicemail node short code and hit the module that way.

Check your IP address of VMPro on your manager config is 169.254.0.2. Change it if it's not. Reboot.

VMPro pumps out through Lan 1 only, you'll never see it on LAN 2.

Please keep us updated i'd like to see a solution.



Kids, Kids, It's Avaya. You're both right.

If you enable NAT on LAN1 (and perhaps proxy ARP in IP routes) you should be able to get to LAN1 from LAN2/WAN


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

Good point amriddle.
I did try NAT between LAN ports the other day. The customer's got peered SIP on LAN 2. The customer called up the next day complaining of one way speech...
Must admit i didn't try ARP. I will run this Monday.

So if i have a UC110 on 10.109.100.251 i would create a route like this?:

IP address 10.109.100.251
Mask 255.255.255.0
Gateway 10.109.100.1
Destination LAN2
ARP ticked.

My understanding from the documentation and your valuable suggestion means this enables any traffic on the network looking for 10.109.100.251 to be answered by IPO LAN 2 to respond on behalf of this IP address.

Could you not set the ARP IP address destination to Lan 1 to leave the SIP alone?

This is a difficult fault to recreate in the lab.

So, hypothesis, the installed and configured UC110 won't automatically respond to ping requests through LAN 1 when it's on a network unless it's told to either by NAT from LAN 2, or an ARP IP address pointing to LAN1.




Kids, Kids, It's Avaya. You're both right.

Maybe try NAT on LAN2 instead, I am never sure which way around to do it tbh


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

BTW the route you mentioned will not work, but after re-reading your post you don't need it, any traffic local to LAN1/2 will not be matching a route anyway as it isn't routed... it's part of the directly attached network. So I think it may be that you enabled NAT on the wrong interface


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

Sorry for the double post, I have had a couple of sociables so my brain isn't 100%
But when using LAN2 will be your PC's default gateway isn't the IPO.
When directly connected to the system you can see it as the IPO is acting as your default gateway, when on the network any traffic from your pc to a non-local address will go to its default gateway which is your router, your router doesn't know the IPO has that address so can't route to it, if you made the IPO your default gateway, or added a route in your router to route it via the IPO address that would also work.

I don't see why when the systems LAN1 is connected to the network it doesn't work....


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

Thanks amriddle. There's plenty to try Monday.



Kids, Kids, It's Avaya. You're both right.

Fixed it, until tomorrow anyway.

The problem was caused by the programming on Port 1 on the 3526 switch. Port 1 has a PVID of the Voice VLAN ID.
'Tagging> tagPVID' Only stops the ping from hitting the UC110 (in this case at least)
Changed Port 1 to untagPVIDOnly and pings now get through from data Lan. VM Client responds therafter.

I'm hoping the DHCP server doesn't fall over during the night. Taking all bets.



Does this help Eyehog, or do you have a totally different set up?



Kids, Kids, It's Avaya. You're both right.

To be honest, this is the first UCM module I've ser up. Thanks so much for the replies, but I have more questions now than before I posted! The problem still needs to be resolved though, so I may just need to get on site and sit down with it, and this forum thread and figure it out.

I always set the default gateway of the UCM as the LAN1 address of the IP office - not had any issues then accessing the VM either connected locally to LAN1 or LAN2 or via ISDN dial in.

In fact I am currently in the process of configuring a new UCM card in a new system via its LAN2 IP address via LAN2 IP Address:7070 and this is without any pre setup.

| ACSS SME |

Pepp77,

I tried doing what you have suggested, setting the default gateway of the UCM to match the IP address of the IPO, and I still cannot connect through the local network, via lan1, or lan2.

How does this even work? How can you have one network cable going from the IPO to the switch, and access both IP addresses? Like I said originally, I can access both IP's when directly, physically connected to the IPO, but when I try to hook the IPO up to the local network, I cannot access the UCM IP at all. Is there some setup on the network side that has to be done?

I apologize for my lack of understanding. Unfortunately, I feel like I am stumbling through the dark trying to get this to work.

Fixed it! I set up an IP route in the IPO the send the UCM IP to LAN1. I think... Anyway it works. I decided I was just going to keep changing things I could change till it worked.

so you can ping the uc on the network just by adding your IP route to the ucm's external ip address?
The IPO should provide this back of house anyway. It'll route automatically to 169.254.0.2 man
test calls internal to visual voice
test calls off the icr to a module ie AAmain

what switch are you using anyway? Are you responsible for it's programming?

using computer in hospital please excuse punctuation.

holdmusic34,

I can ping the UC on the network, yes. I went to the IP Route section in Manager and set the following (see above). 172.16.0.122 is the IP of the UCM, (172.16.0.121 is the IPO), and 172.16.0.1 is the default gateway of the local network, and LAN1 is the port I am using the go to the local network (LAN2 is unused).

I would have expected it to do that on it's own interaly, but obviusly it wasn't. Everything this else I tried did not work, but as soon as I made this change, it worked.

Everything else seems to work as well, so it doesn't look I broke anything doing this.

I'm not sure what (network) switch it is (Not on site now), and no, we are not responsible for it. The phone system is an IP500 V2 running 8.43.