Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

4620SWIP says...discover 172.20.xxx.xxx

Status
Not open for further replies.
Oct 4, 2006
36
US
Hi guys,

this one might be over my head but I figured I'd ask the questions before I decide on kicking it up the ladder. We have a S8300 in the office and have a number of subnets connected to it. We are planning a trip out to Vegas and want to get some phones up and running over a site to site vpn. We have the site to site up and running, the phones pull DHCP (172.20.100.x) and appear to get the correct DHCP info. I went in and added to the network map

172.20.100.50 172.20.100.75 Region is 2 vlan N

Region 2 is used by one of our internal subnets..

The phones are basically coming up with Discover 172.20.2.10 (our phone switch).

I usually use GEDI to get around on the switch, so i'm not sure if I'm missing something. I don't know how to ping or check the IP routes from the switch to see if it is a connectivity issue.

I'm more of a network/windows guy.. so forgive me.. I have learned a lot on the phone switch, but know my limitations..
 
you either have some ports blocked by a firewall, or the Processor Ethernet (S8300) IP is unreachable. It is definitly a networking connectivty issue.



Mitch

AVAYA Certified Expert
 
Mitch,

how can I check to see if I can ping from the switch (172.20.2.10) to the phone (172.20.100.50)? Also is it ports 1719 and 1720 that need to be opened? I think we are wide open for firewall rules on the site to site.

Or do I just need to place a laptop on the network and see if I can ping to the phone.


RS
 
I went into the maintenance web interface and i am able to ping the phone (172.20.100.50 and .51) Traceroute looks fine.. any other thoughts on what to check?
 
there are many, many other ports, such as 1719, and ports in the 61XXX area for TCP control, not to mention several thousand UDP ports defined in the IP network Region form (UDP ports).

I suggest you install the IP softphone or the AVAYA One-X client on a notebook PC and try to login locally, then bring the notebook PC onsite, and it will probably still fail... proving some ports are being blocked.

You can load "ethereal" on the PC and see what is being transmited and not making it through.



Mitch

AVAYA Certified Expert
 
If using 16xx or 96xx on HTTP:
Are the DHCP options in option 242 pointing to the webserver where your images are, and can the phone get onto the vlan the server is in? You may be getting a DHCP on the phone, but it might not be supplying the options it needs.
Do you get a 200, or a 40x http message on the screen while booting? in case of booting the http image it should point to the http server (not the S8300)
If booting TFTP image, can you connect with a pc using a TFTP client? in other words can you reach the TFTP port of the CM?

 
The phones are 4610s and 4621s SW IP. Below is from the tech that is on the other end with the phone

"The phones appear to be getting the info. I stepped through the phone config, it is as follows

As boot it states loading ______4.bin then 46xxsettings.txt

Then goes to Discover 172.20.2.10

Then if I check the settings I find:
Phone 172.20.100.51
CallSV 172.20.2.10
CallSV port 1719
Router 172.20.100.253 /24
FileSV 172.20.1.73

If I run a packet capture on 172.20.100.51, I see traffic between it and 172.20.1.73 via port UDP 1026 so we appear to be passing traffic from 172.20.100.x and 172.20.1.x"

Had him put alaptop behind the Vegas Sonicwall and allowed it to obtain an IP from your DHCP server. I received 172.20.100.52 and he was able to ping 172.20.2.10 without issue so it appears like the communication or at least ping is working to the 172.20.2.x network.

Other than the ip network map, is there anything else I should change?


 
perhaps the IP-Network-Region's connectivty options are not set up properly.

try changing the IP-Network-Map and not defining this new site, see what happens then. If it works, then check your interregion connectivty codec sets used, that could be the issue.



Mitch

AVAYA Certified Expert
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top