IR 2.0 and CM 4.0 voip inegration

[GuzaPasha]

Hi all,

has anyone experienced that the voip channel are in foos state. While trying to change it to manoos than to inservice, system says channel is down, channel state changed to foos.

In the voip configuration screen, there is the CM version than should have been choosed, but the choices are only CM 2.0 and CM 3.0. Any ide? Could this be a problem.

I tried to configure stations like H.323 as well as 7343ND(softphone y).

There are 2 NIC interaces on the IR, one to the VLAN where CLAN and MEDPRO reside, and the second one to the customer network..

Regards,

Marko

 

[GuzaPasha]

Anyone to know?

Guzapasha

 

[Doyaya]

Did you change IP address on IR?

 

[GuzaPasha]

Hi Doyaya,

we have changed the IP address, but only on the bge0 which we want to use for customer LAN and not changed on bge1 which is planned for ip softphone registrations. bge0 and bge1 were configured via serial management port and later on bge0 was changed.

Have you experienced the same?

looking forward for your answer

 

[Doyaya]

When you change ip address or hostname AIR goes to the restricted mode . Everything looks perfect but you cannot change the state of voip channels. You must reinstall AVlm package, but read first doc on following link (PSN# 870U):

http://support.avaya.com/japple/css...285644&temp.bucketID=162024&PAGE=Document

 

[GuzaPasha]

Hi Dojaja

Thanx for this info, i've already tried this without success.

My main concern is the type of CM? why is that field used?

do you have CM 4.0 connected to this?

Maybe sth is wrong in the initial solaris setup? Is there any way to start over again without installing solaris.

Network connection looks fine, able to ping, telnet, i will explore the mst trace in the meanwhile...