Help Avaya 8.1

[Vapour84]

Good Afternoon everyone,
I'm in a pickle right now. Last few days our phone system is not picking up dhcp. the phone says "vlan =300" we did an network upgrade over the weekend.

We have an Avaya ip office manager 8.1. we have gone from 192.168 to 10.128. our phone supplier no longer wants to be involved (as it no longer supported) so i'm taking over the system,

we have a switch but we don't know who installed it and i cant get a console cable on the switch as we don't know the password to access it. i've connected a laptop directly onto the switch and can see it's picking up an ip address and subnet.

we have two connections lan1 which is going into our new switch with vlan 100 enabled.
Wan1 is going directly into the switch,

i've changed the lan1 to our new network ip : 10.128 and made sure dhcp is disabled. i havent touched voip on lan1

Lan2 the ip is different 10.253 but dhcp mode is enabled and pool is set to 100. start address is 101.

is there anything i need to do to get this working?

 

[snowman50]

So you have proved the system is sending out dhcp and phone works.

Did you try to reconnect the phone back to the Cisco switch after it received the new settings to see if it reconnects.

Look at the settings of the phone and see what info it has now picked up

Also you stated the ipo dhcp is set to 100 phones and you have 250 phones ?.
To me that means only 100 phones will get dhcp.

You could also CLEAR one ip phone settings and let it reboot to see what info it picks up.

 

[Vapour84]

i did plug it back into the port and it didn't pick up any dhcp.

i had to do an inventory yesterday so we have 250 phones. but only 100 get used the rest got removed now.

might factory reset a phone see what it's picking up.

 

[Vapour84]

@snowman50. finally got it working... it was iproute... the old phone supplier deleted it looking in the logs.

now i have another issue. the whole office phones working fine... we have a massive warehouse but they aint getting dhcp which is weird...

also got monitor working.....

i got this issue now...

 

[Vapour84]

08:06:09 62224991mS CMMap: a=2.1 b=21.42 CheckSpeechPathMonitor (pcp[44]b1r0) unregister
08:06:09 62224991mS PRN: Confer DSP: disabled DTMF detector 0
08:06:09 62224991mS PRN: Confer DSP channel 0: freed DTMF detector 0, 24 free
08:06:09 62224992mS CMMap: PCG::UnmapBChan pcp[44]b1r0 cp_b f5810e18 other_cp_b f581d880
08:06:09 62224992mS CMMap: a=2.1 b=21.42 M02
08:06:09 62224992mS H323Evt: SetOperational 13 10.253.8.19:49152 to 0
08:06:09 62224992mS CMMap: PCG::UnmapBChan pcp[138]b0r1 cp_b 0 other_cp_b 0
08:06:09 62224992mS H323Evt: RTP(END): 10.253.8./49152 10.253.8./51440 CODEC=Alaw64K(4) PKTSZ=160 RFC2833=off AGE=9696 SENT=398 RECV=404 RTdelay=0 jitter=0 loss=0 remotejitter=0 remoteloss=0
08:06:09 62224994mS CMMap: a=2.1 b=0.0 Mapper::FreeCodec freed CMRTVocoder resource busy 1, total 32

 

[Vapour84]

08:06:09 62224986mS CMMap: a=21.42 b=0.0 T0

 

[derfloh]

Who is the DHCP server? IF IPO is the DHCP server, enable Services\DHCP in SysMon to see if DHCP requests reach the IPO or not.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Vapour84]

@derfloh

09:21:02 525122mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01
09:21:02 525122mS DHCP: DHCP::Request from non-Avaya IP Phone {CC96E5A73054}
09:21:02 525833mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01
09:21:02 525833mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01, 10.253.8.118
09:21:02 525833mS DHCP: DHCP::SetState, 10.253.8.118: Offering->Checking
09:21:03 526020mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01
09:21:03 526020mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01, 10.253.8.124
09:21:03 526020mS DHCP: DHCP::SetState, 10.253.8.124: Offering->Checking
09:21:03 526114mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01
09:21:03 526114mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01, 10.253.8.158
09:21:03 526114mS DHCP: DHCP::SetState, 10.253.8.158: Offering->Checking
09:21:03 526333mS DHCP: DHCP::SetState, 10.253.8.118: Checking->Offering
09:21:03 526520mS DHCP: DHCP::SetState, 10.253.8.124: Checking->Offering
09:21:03 526615mS DHCP: DHCP::SetState, 10.253.8.158: Checking->Offering
09:21:03 526968mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01
09:21:03 526969mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01, 10.253.8.106
09:21:03 526969mS DHCP: DHCP::SetState, 10.253.8.106: Offering->Checking
09:21:04 527386mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01
09:21:04 527386mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01, 10.253.8.157
09:21:04 527386mS DHCP: DHCP::SetState, 10.253.8.157: Offering->Checking
09:21:04 527469mS DHCP: DHCP::SetState, 10.253.8.106: Checking->Offering
09:21:04 527881mS RES: Wed 7/8/2024 09:21:04 FreeMem=58059968(3) CMMsg=2 (2) Buff=5200 941 1000 6402 5 Links=28161 CPU=11/13/7688/14903/148185/0
09:21:04 527881mS RES2: IP 500 V2 8.1(52) Tasks=45 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=72 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=2 SSA=0 TCP=19 TAPI=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
09:21:04 527886mS DHCP: DHCP::SetState, 10.253.8.157: Checking->Offering
09:21:05 528733mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01
09:21:05 528734mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01, 10.253.8.133
09:21:05 528734mS DHCP: DHCP::SetState, 10.253.8.133: Offering->Checking
09:21:06 529235mS DHCP: DHCP::SetState, 10.253.8.133: Checking->Offering
09:21:07 530018mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01
09:21:07 530018mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01, 10.253.8.122
09:21:07 530018mS DHCP: DHCP::SetState, 10.253.8.122: Offering->Checking
09:21:07 530518mS DHCP: DHCP::SetState, 10.253.8.122: Checking->Offering
09:21:09 532353mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01
09:21:09 532354mS DHCP: DHCP::Request from non-Avaya IP Phone {F4EA6786423E}
09:21:09 532823mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01
09:21:09 532823mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01, 10.253.8.153
09:21:09 532823mS DHCP: DHCP::SetState, 10.253.8.153: Offering->Checking
09:21:09 532900mS RES: Wed 7/8/2024 09:21:09 FreeMem=58055744(3) CMMsg=2 (2) Buff=5200 940 1000 6402 5 Links=28148 CPU=12/18/7688/14519/148185/0
09:21:09 532900mS RES2: IP 500 V2 8.1(52) Tasks=45 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=71 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=2 SSA=0 TCP=19 TAPI=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
09:21:10 533323mS DHCP: DHCP::SetState, 10.253.8.153: Checking->Offering
09:21:11 534084mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01
09:21:11 534084mS DHCP: DHCP::Request from non-Avaya IP Phone {AC91A1936225}


now the whole phone systems gone down i havent made any changes

 

[derfloh]

Looks as if the network would be OK. In SysMon you can enable the filter checkbox "Development Tracing" under "System". Then in the menu "Status" you will find an entry "DHCP Data" where you can see what IPs are used and bound and so on

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Vapour84]

Thanks you for your help.

so i need to trace why the warehouse is not working, at least office is back to normal.

10:43:10 4264277mS CMMap: a=21.39 b=4.24 M02
10:43:10 4264278mS CMMap: a=21.39 b=0.0 T0
10:43:10 4264278mS CMMap: a=21.39 b=0.0 DTMF::~DTMF freed CMRTTonegen resource busy 5, total 8

10:43:04 4258857mS CMMap: PCG::UnmapBChan pcp[112]b1r0 cp_b f57a7c08 other_cp_b f580201c
10:43:04 4258857mS CMMap: a=2.1 b=4.24 M02
10:43:04 4258857mS H323Evt: SetOperational 8 10.253.8.19:49152 to 0
10:43:04 4258857mS CMMap: PCG::UnmapBChan pcp[129]b0r1 cp_b 0 other_cp_b 0
10:43:04 4258858mS CMMap: a=21.39 b=0.0 DTMF::AllocateRAS allocated CMRTTonegen resource busy 6, total 8
10:43:04 4258858mS CMMap: a=21.39 b=1.255 T
10:43:04 4258858mS CMMap: a=21.39 b=4.24 M22
10:43:04 4258858mS H323Evt: RTP(END): 10.253.8.19/49152 10.253.8.102/49702 CODEC=Alaw64K(4) PKTSZ=160 RFC2833=off AGE=16624 SENT=822 RECV=818 RTdelay=0 jitter=0 loss=0 remotejitter=0 remoteloss=0
10:43:04 4258859mS CMMap: a=2.1 b=0.0 Mapper::FreeCodec freed CMRTVocoder resource busy 1, total 32

I'm also getting this red error when people pick up calls.