1120 IP-set dont work on local LAN.

[geirendre]

Hi, I have this strange problem when trying to set up new IP sets.
If I try to connect them to the same LAN as the SS is on,
it gets all the IP-setup it needs from the DHCP-server, and I put
in the IP-address of the SS manualy.
The set will then reboot and try to connect to the SS, but fails,
"server unreachable"
I can ping the set from the SS, and ping the SS from the set.

The strange ting is that if I move the set to a different site,
(different LAN connected via WAN to the LAN with the SS)
the set finds the same SS, connects to it and works perfectly.

So it will not register on the SS if it's on the same LAN as the SS is,
but if it's on a different LAN it will.

Does the SS have some setting that would disable local sets?
or what can it be???

 

[Firebird Scrambler]

It sounds like a port problem. I'm guessing that you are NOT using the ELAN for IP phones?.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[geirendre]

Regarding "Port problem"
It uses port 4100 both for WAN(when it works), and LAN(when it fails).
At least thats whats defined on both the sets and on the SS.

Yes LAN = TLAN

1120set------Router------Switch------TLANswitch------SS = works

1120set------Switch------TLANswitch------SS = dosn't work.

.

 

[nessman]

Are you 110% sure you didn't fat-finger the keypad when entering the IP address for the sig server? Can you go into network diagnostics on the 1120e and ping the sig server (or anything else on the network where the sig server resides)? And if you're using DHCP, why aren't you letting the DHCP server options tell the phone what IP address is the sig server instead?

 

[geirendre]

Hi.
Yes I'm 110% sure of the IP address, and as stated in my 1.post,
I can ping the SS from the set.
I have set up several sets, and it's been the same for all
sets, they fail on the local LAN, but works fine when sent out to a
user on another site, and registering on the same SS.

I don't run the DHCP server.

 

[nessman]

With VoIP phones, the phone guy and the IT guy needs to get on the same page then. The lines between telecom and IT are very much blurred. Anyway, getting off my soapbox...

You got some sort of network issue going on here... VLAN? Subnetting?

It's best you get chummy with the IT guys and work this one out.

 

[Tman45]

My guess is that you need to make sure the VLAN is set to NO as if you are trying to connect to the same LAN as the SS there won't be a VLAN. Since you are using the setup defined by DHCP to try to get a local phone working it is going to try to use a different VLAN (if you have DHCP setup that way) and I think for a local route to go out to another VLAN and back to a local LAN sounds like a loop that should be prevented.

I have set IP phones to no for VLAN and have got them to register.

 

[geirendre]

OK, just a quick update on this:
I finally figured out what the problem was.
By tracing the IP-packets from the Set all the way in and out
of each switch on the way from the Set to the SS, I found that
the packets stopped in the last switch (where the SS, CS etc
are connected together and connected to the LAN), referred to as
the TLANswitch in my previous post.
The packets was coming in on the LAN port of the switch,
but not being forwarded out on the port leading to the SS.

Replaced the switch and the Set came up instantly.
Wireshark (and tcpdump) are nice tools to use when
strange tings like this happens.

Thanks for the feedback folks