remote 5610 stuck on DHCP (timer running)

[Ballinea]

Hi

One of our remote users moved house and with it a new ISP a the new location.

When she plugs in the 5610 phone, it loads the i10VPN23252.bin as normal, indicates 'Starting' and then it hangs in the DHCP with he timer clocking up to infinity.

When she tried her old ISP at her old location it worked, but problem is she is in a new home and stuck with the new ISP

Can anyone let me know what is being blocked so we can address the issue with the ISP

It like some protocol or port is being blocked ( or both )

We called the ISP but they said they do not block anything - but I dont belive them.

The ISP in located in Dublin, Ireland - called UPC ( UPC.ie )

Thanks in advance for your help

Pat

 

[amriddle01]

The issue is her new router isn't issuing an address to the handset, it's falling at the first hurdle. Nothing to do on the handset until that gets fixed


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[Ballinea]

Thanks for the reply

The router at the new location is a CISCO EPC 2425

Do you think there are any settings we can change in the router to resolve this or is it a router specific problem.

We did get the ISP to log in to the router when the phone was plugged in and they said they could see that there was a device plugged in to the port but they said there was no traffic passing

Thanks

Pat

 

[hairlessupportmonkey]

Ive seen 5610 and newer do this.

A power cycle of the handset normally sorts it.

ACSS - SME
General Geek

 

[Ballinea]

Thanks for reply - We tried many things including power cycles to no avail.

 

[DrDrayAvaya]

just static assign address info in the meantime, presuming other devices get DHCP ok, like PC's etc. find the router address manually, call server etc. "Press * to Program"

 

[tlpeter]

That is what i always do.
It boots a little bit faster too


BAZINGA!

I'm not insane, my mother had me tested!

 

[DrDrayAvaya]

definitely quicker! or put a SPAN /wireshark on and see what the DHCP messaging looks like (if at all) coming from the cisco. is it trippin on the SSON side of things maybe? or is the cisco actually just bridging the ISP static and you need another SOHO router after that? in NZ we can't get a /29 routed range on ADSL2+ circuits for instance.. hard to tell what's goin on there tho. (what's meant to be going on i mean!) i'm prob way off target!?

 

[hairlessupportmonkey]

DrDrayAvaya,

Im keen to talk to you about IPO based roles in NZ......



ACSS - SME
General Geek