I am currently trying to figure out how to add an ADTRAN 712 phone to our NETVANTA 7100. I have the phone configured properly, but it does not connect. On the NETVANTA side, it says it is not SIP registered but despite everything I have tried to do, I cannot figure out how to get the phone to register with the SIP server. I have looked at documentation for both the server and the phone but they are very general. Does anyone have experience with this that they might give me some ideas on what I need to do on the phone or server end to register the IP/Phone with the server?
hiattech,
What switch port is that phone connected to is it connected directly to the 7100 or is connected into another switch? I would recommend verify the switch port it is connected to is configured correctly. In example I see from the config port 3 is set with Voice VLAN on 1 instead of 2. If you are using other switches ensure the port the phone is connected to is trunked on VLAN 1 and VLAN 2, then make sure the upstream switch ports are trunked on both VLANS as well as the 7100 port. Based on your configuration the phone should get DHCP from the 7100 and receive a VLAN 2 IP Address of 10.10.20.X. Check the phone status by hitting Menu, Phone Status, Network down arrow to the IP address if it is not getting a 10.10.20.X IP address it is most likely VLAN issues. If it is getting a 10.10.20.X IP address delete the phone entirely and rebuild it as it maybe a corrupt phone config file.
John Wable
I assume you have done this, but verify the MAC address of the phone with the config file in the 7100 IP Phone Configs menu.
Log into CLI of the 7100 and go to enable mode
Enter:
Debug ip dhcp server
Debug ip ftp-server
debug sip user-registration
Then go to phone and press menu button then 2. Phone directories > then 9. Reset > then press the Factory soft key button.
The phone will default and then after the phone is done booting up, post the debug output here.
-Mark
I have indeed checked the MAC address. The phones were all configured with the appropriate MAC and IP address. To add to the chaos, there was a power outage Wednesday and 2 of the phones have lost their SIP registration. When i ran the debug for dhcp, i got "ambiguous command". I don't think the phones DHCP to the server because it's on VLAN2 but I'm not sure if it should still find the network.
That said, if I'm not mistaken, when debugging, it should print output along the screen while it is running correct? If so, nothing came up with that debug running. Should I try to put in the DNS and gateway so it can try?
Thanks
The debug dhcp command has changed so it might be different if you have older firmware.
Have these phones worked in the past with this 7100.
The easiest and probably most helpful is if you attach your config file. Make sure you include the voice settings when u download it from the GUI. Let me know which users are having the problem
Make sure you remove any passwords if in clear text.
-Mark
I managed to get the other 2 phones back online; all they needed was the IP config (basic network settings) put in again and they picked right up. There are currently 4 working phones. I'm not sure if this specific phone has ever been configured with this system, but the same model has worked fine. I went into the admin page on one the of phones before I set it back to it's original config and took the admin settings and applied them to the new phone (adjusting the extension as needed), but that didn't do any good. I'll get the config file shortly and post it here shortly.
hiattech,
What switch port is that phone connected to is it connected directly to the 7100 or is connected into another switch? I would recommend verify the switch port it is connected to is configured correctly. In example I see from the config port 3 is set with Voice VLAN on 1 instead of 2. If you are using other switches ensure the port the phone is connected to is trunked on VLAN 1 and VLAN 2, then make sure the upstream switch ports are trunked on both VLANS as well as the 7100 port. Based on your configuration the phone should get DHCP from the 7100 and receive a VLAN 2 IP Address of 10.10.20.X. Check the phone status by hitting Menu, Phone Status, Network down arrow to the IP address if it is not getting a 10.10.20.X IP address it is most likely VLAN issues. If it is getting a 10.10.20.X IP address delete the phone entirely and rebuild it as it maybe a corrupt phone config file.
John Wable
Is the phone directly plugged into the 7100? If so what port?
Config looks ok. Phone config files looks ok.What we need next is a debug capture of the phone botting up.
Telnet or SSH into theCLI of 7100 not serial and enter, make sure your buffer on your terminal program is set high:
Debug ip ftp-server
Debug sip stack mess
Debug sip user-registration
From the 712 phone, go to menu > 2> 9 and then select the factory button.
Copy the debug and put it into a text file. Save it and then reply to this email and attach the file. That is the easiest way to attach a file to a post.
-Mark
hiattech,
By the way I took a closer look at the supplied config and see you have 6 SIP users but only see 4 properly configured voice ports on the 7100 port 1 and 2 and ports 4 and 5. On your uplink port you do not have VLAN 2 enabled so if the other users are connecting off another switch it looks like you need to add VLAN 2 to the allowed VLAN list on port Gig 0/2 also make sure and edit port 3 to have a voice VLAN 2 instead of 1.
John Wable
I'll check that out jwable. This is the only switch in the building (very small company) so it's not connecting to another, but I'm guessing enabling that might be a good idea anyway? Despite it showing DHCP for 192.168 and for the 10.10 networks, the computers (192.168) actually get DHCP from a separate router. I'll adjust the VLAN on port 3 as well and let you know. I'm pretty sure that phone is on that port.
Yeah I noticed the voice vlan 2, that is why I asked him to see what port the phone was plugged into.
Good work John. Interesting how the phone just quit working and how that setting got changed.
-Mark
Mark,
The way I read it this phone never worked. There were two other phones that quit working after a power outage but them came back up.
John Wable
I should clarify on the phones not working part. As far as I know, this phone hasn't worked in I'm not sure how long. 2 other phones lost their network configurations during a power outage and I had to manually reprogram them but they picked right up. I'm hoping/guessing that if I set that 1) if I set that VLAN on the port to 2, it'll connect and 2) if I turn on the trunking for VLAN 1 and 2 on the gigabit port, that, in theory, the phones should connect and pick up their configurations on their own from this point out. Is that about right?
One more question: can I get some clarification on this? "If you are using other switches ensure the port the phone is connected to is trunked on VLAN 1 and VLAN 2, then make sure the upstream switch ports are trunked on both VLANS as well as the 7100 port."
We don't have any other adtran switches, but we do use an ASUSTek RT-N66W for the DHCP, VPN, and WiFi.
hiattech,
If any phones are connected to the ASUSTek then it will need to do VLANing and have VLAN 2 enabled on the port that connects to the 7100 and also any port the phones are connected to. In addition since you have another device handing out DHCP you will want to configure as well with DHCP option 157 like in the Adtran config supplying the proper user name and passwords:
option 157 ascii TftpServers=0.0.0.0,FtpServers=10.10.20.1:/ADTRAN,FtpLogin=<>,FtpPassword=<>,Layer2Tagging=True,VlanID=2
Or alternatively you could manually configure the phones with the VLAN 2 VLAN ID. Here's the boot scenario:
Phone Powers UP
Phone sends out DHCP request
Phone looks for DHCP Option 157 to get the information needed to connect to 7100 to download config file
Phone receives Option 157 and sees it should use VLAN 2
Phone reboots using VLAN 2
Phone sends DHCP request on VLAN 2
Phone gets information on where to download it's config file
Phone downloads config
Phone registers with 7100
If the phone does not get Option 157 then it will just boot up on the IP subnet it gets DHCP for so if it gets it from the other DHCP device instead of the 7100 it wont boot up right.
If the phone can not find it's specific config it will boot up on a default config.
Does that help explain it?
John Wable
That does help. The computers and the phones all connect directly to the 7100, and the 7100 connects to the ASUS for DHCP. The ASUS connects to the modem. It occurs to me though that if the ADTRAN can do the DHCP, then the ASUS is somewhat redundant . . .
Ok, final update on this topic. There were a couple right answers. First, the port being on the wrong VLAN was part of the problem. I also found that enabling the trunking for VLAN 1 and 2 helped the phones be able to DHCP instead of having to be set static. Finally was an issue we hadn't noticed; that of the port 18 not being set to power inline never. The phone as acting like it wasn't even seeing an FTP server which I thought was very strange.
So finally, after all the reconfiguring and such, I got fed up and decided to try the port directly. The phone booted up with the right configuration and registration just fine. So I took the phone back to the desk and was back to the same problem. Double checked the port and found it wasn't lit up. Apparently, the line was plugged into 18 which gave it power, but nothing else. Hours of frustration due to that. Teach me to check that a bit closer . Thanks for all the help.