[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Unable to obtain IP Address over DHCP
Author Message
randompunteruk Offline
Junior Member
**

Posts: 1
Joined: Sep 2013
Reputation: 0
Post: #1
Unable to obtain IP Address over DHCP
Hi,

We have a number of Yealink T22P phones, including a new batch.

We have determined that the phones are unable to get an IP address over DHCP when plugged into some switches around the office.

I can see that the phone is sending out a lot of discover messages and getting some responses, but never sending out a request message as far as I can tell:

Code:
23764 779.088203000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0xd11fdc42
  23796 781.035201000  0.0.0.0               255.255.255.255       DHCP     590    DHCP Discover - Transaction ID 0xb25c3e3d
  23797 781.036463000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0xb25c3e3d
  23817 782.177730000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0xd11fdc42
  23861 784.131779000  0.0.0.0               255.255.255.255       DHCP     590    DHCP Discover - Transaction ID 0xb25c3e3d
  23862 784.132857000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0xb25c3e3d
  23944 785.268454000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0xd11fdc42
  23988 787.255461000  0.0.0.0               255.255.255.255       DHCP     590    DHCP Discover - Transaction ID 0xb25c3e3d
  23989 787.256554000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0xb25c3e3d
  24646 808.549804000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0xe943470a
  24713 810.721273000  0.0.0.0               255.255.255.255       DHCP     590    DHCP Discover - Transaction ID 0x56b26e7a
  24714 810.722178000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0x56b26e7a
  24739 811.645492000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0xe943470a
  24776 813.829975000  0.0.0.0               255.255.255.255       DHCP     590    DHCP Discover - Transaction ID 0x56b26e7a
  24777 813.831205000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0x56b26e7a
  24800 814.729657000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0xe943470a
  24866 816.975310000  0.0.0.0               255.255.255.255       DHCP     590    DHCP Discover - Transaction ID 0x56b26e7a
  24867 816.976544000  10.1.1.8              255.255.255.255       DHCP     388    DHCP Offer    - Transaction ID 0x56b26e7a

I can also see that some of them are getting jumbled up.

It seems to be giving up on DHCP discovers very quickly, so it could be getting very confused.

Windows machines are getting addresses fine, but I believe that the wait a while for responses and then use longer and longer timeouts.

We do go through a couple of layers of switches, which I think might be contributing to the problem by slightly delaying responses. We did make changes to the switches a couple of weeks ago.

Is there a way to make the phones wait longer for a response from a DHCP server?

Has anyone else seen similar problems?

Thanks for any insight anyone can offer.

Ashley
09-30-2013 07:31 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
rcaskey Offline
Junior Member
**

Posts: 2
Joined: May 2013
Reputation: 0
Post: #2
RE: Unable to obtain IP Address over DHCP
I encountered this with a switch that had a few ports configured not to use RapidSTP. Without RapidSTP it took about 30 seconds for the link to come up and so as a result it timed out and DHCP timed out before the link as up. Enabling it fixed it right up.

Might want to double check both that the switches have RapidSTP enabled and all the ports that have phones plugged into them have RapidSTP enabled.

I do agree it is annoying that it is pretty much required but in fairness users and Windows expects it these days as well - Windows will time out reconnecting network shares as well if RapidSTP isn't enabled.

-Rob
09-30-2013 10:15 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  No IP address for W60 but T42 working ok heathb 2 712 03-09-2022 05:11 PM
Last Post: complex1
  DHCP not working on T26P when OpenVPN is enabled. LandonL 11 28,029 05-12-2021 10:46 AM
Last Post: 1sae
  speed dial to an IP address (ext@IP on value) EduardoV 3 5,084 11-07-2019 07:43 PM
Last Post: EduardoV
  how toadd image in remote address book of yealink phone? Olkan 1 5,829 07-28-2017 02:12 AM
Last Post: Samuel_Yealink
  T42G dhcp issue Neway 1 6,420 06-15-2017 03:01 AM
Last Post: Karl_Yealink
  Unable to get OPUS codec to match asterisk 13.13.1 scully 3 7,262 01-21-2017 03:29 AM
Last Post: Jensen_Yealink
  T46G Hostname not registering on DHCP fraukas 2 10,229 10-27-2016 12:34 AM
Last Post: fraukas
  t32g Won't Obtain IP markbad311 0 4,805 06-25-2016 02:04 AM
Last Post: markbad311
  Yealink 48G unable to redial +44 numbers DCoates 1 6,810 05-13-2016 01:25 AM
Last Post: complex1
  T46G Not Time Syncing to DHCP or NTP pete333 1 7,349 01-05-2016 05:19 PM
Last Post: Klaus_Yealink

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication