Nortel CS1000 IP Phone Registration issue 1

[mshahrukhali101]

Kindly Help,

We have 3 different networks
192.168.202.1 the node IP of CS1000
192.168.202.0
All IP phones Working fine.
10.200.200.0 Customer LAN at one City
All IP Phones working fine
10.150.200.0 Customer LAN at Other City
IP phone Registration Error

02/02/2016 16:26:09 LOG0004 tRUDPSS: Forwarding for connect Id = 773241464, erro
r of type = 6 (connection lost).
02/02/2016 16:26:09 LOG0003 tRUDPSS: Delinquent connection 0x2e16ba78 lost betwe
en [192.168.202.1:4100] and [10.150.200.66:5000], previous status was -1

All Sides can ping each other and there is no issue in network.

 

[MikeRizz]

Have you verified the actual phone itself has the correct info in it, SS 1, VLAN, etc. ?

 

[KCFLHRC]

A simple ping means nothing. If I had a dollar for every time someone said the network has no issues and then to find out it does then I wouldn't be a lot wealthier.

 

[bignose21]

Phone looks to be on port 5000 tried 4100?

 

[mshahrukhali101]

Phone settings are fine having right node IP.
even i have provide them a soft phone 2050 for testing but resulting in a same error.
I have changed the port from 4100 to 5000 no success.

we have updated patches at CS and SS as well.

signalling server is not pinging the city network (10.150.200.0) after we update patch.

is there any routing we have to add to SS.

 

[golfdoctor]

Hard to tell - however this seems to be a network issue wrt 10.150.200.0
Firewall, configuration, hard to tell.

- is this a new install or did things just stop working ? If the latter what changed ..
- You will need to be able to ping the gateway or something on 10.150.200.x regardless. Once this is confirmed, at least you know the pipe/highway is present.(does not mean your phones will work/register - but there is no chance if no highway)
- if a highway available take an 1120/1140/2002/2004 (serviceable hardware unit) and manually configure with a staic IP at the 10.150.200.x end to see what happens.
- the list could go on and on...

Only some thoughts.....


TGD

 

[mshahrukhali101]

Dear golfdoctor
thing are working fine week ago it just stop working. both sides can ping each others but signaling server cant ping other side.
we are testing with network as well but is there any routing we can add on SS feil, if is that so how can we do so?

 

[golfdoctor]

I suppose the routing question is dependent on how your network is configured. Your network people can assist you.
On all my nodes I have never added anything extra to the routing tables associated with the nodes.
Normally the defaults work after the SS is initially configured. Any layer 2 or layer 3 networking stuff is left to the network group - you are simply implementing the network parameters they provide.

Sure seems to be a network config or finger issue associated with 10.150.200.x . After the patching did the other remote location experience the same issues? Are the IP phones SIP or UNIStim ?
Can your SS ping anything ?
Maybe a trace route from the SS will assist with the fault finding journey ....



TGD

 

[mshahrukhali101]

Both side pinging each other after patching

from any computer at 192.168.202.x we can ping 10.150.200.x
and also from 10.150.200.x to 192.168.202.x

can you please tell me how to run trace route command from the SS?
at any computer tracert command is working fine from both ends.

 

[golfdoctor]

So you can ping the node IP 192.168.202.1 ?
Same command as you identified. Login to SS and implement - use the proper credentials admin2 or root - can't remember.

It might be an idea to get your network team or your vendor involved for some assistance.


TGD

 

[KCFLHRC]

Certainly sounds like a firewall issue. Make sure they have all the ports opened up for the voice and also make sure there are no SAL rules defined.

 

[mshahrukhali101]

how to run trace commands on SS, still a Mystery.

oam> help trace
General trace tool commands:
traceAllOff Disables the trace facilities from writing to the TTY, SYSLOG, and specified files
traceAllOn Allows the trace facilities to resume writing to the TTY, SYSLOG, and/or specified files
tracePrintOff Disables the trace facilities from writing to the TTY
tracePrintOn Allows the trace facilities to resume writing to the TTY
traceFileOff Disables the trace facilities from writing to the SYSLOG, and specified files
traceFileOn Allows the trace facilities to resume writing to the SYSLOG, and/or specified files
traceShow Displays the configured trace tools that may currently be active
oam>
@KCFLHRC
no firewall is stopping it but i m not sure about SAL.

 

[golfdoctor]

What release are you running ? (linux or VxWorks software)

If VX Works you probably need to go into PDT - vx shell
If Linux after logged in you may need to go to the su account.

SSH into your SS IP (TLan IP) or use the com port as a direct connection -
tracert 10.150.200.x
(x is the gateway IP or a known working device at the remote location from the SS perspective)


TGD

 

[golfdoctor]

Forgot to mention to please post the tracert results


TGD

 

[mshahrukhali101]

We are using release 5.0 VxWork.
I will surly post the result if I got successful to run trace route command.I don't know what to do here?

pdt> help
For help on a particular command group type: help 'group'
Available command groups are:

Accounts User account administration
DLOG f/w download log file commands
ISEC Intra System Signaling Security CLI commands
Network remote access commands
PDT PDT built in commands
Patcher Patch Commands
RID remote iset diagnostics commands
SSH SSH commands
UFTP UFTP IP telephone f/w download commands
disk File system maintenance and diagnostics
election Election module commands
elm ELM module commands
emhelp EM Help File related commands
iset iset module commands
mam MAM module commands
ncs Network Connect Server module commands
npm Network Protocol Module, module commands
nrsDB Network routing Service, module commands
nrsomm Network Routing Service OMM display commands
pbxlink PBX link commands
rdtools Help for rd tools
securityShell Security shell commands
sipctiomm SIP CTI OMM display commands
system System administration commands
tps tps module commands
trace General trace tool commands
uipc Universal ISDN Protocol, module commands
ums UMS module commands
usi UNISTIM related commands
vte Vitrual Terminal Emulator related commands
vtrk Virtual trunk, module commands
pdt> help trace
trace
General trace tool commands:

traceAllOff Disables the trace facilities from writing to the TTY, SYSLOG, and specified files
traceAllOn Allows the trace facilities to resume writing to the TTY, SYSLOG, and/or specified files
tracePrintOff Disables the trace facilities from writing to the TTY
tracePrintOn Allows the trace facilities to resume writing to the TTY
traceFileOff Disables the trace facilities from writing to the SYSLOG, and specified files
traceFileOn Allows the trace facilities to resume writing to the SYSLOG, and/or specified files
traceShow Displays the configured trace tools that may currently be active
pdt>

 

[golfdoctor]

Yikes - Old release - I believe I'm wrong about the tracert command within VxWorks (Rlse 5.0)

I don't have a SS running Rlse 4.5 - 5.5 so I'm guessing here
ping might be all you can do from the box - does that work ?

Not sure if this will work or not but worth trying - may need to be in vxshell
Use exact syntax as shown - replace the variables for your situation

Example Only:
rTraceRoute "source", "destination", "max hops"
rTraceRoute "47.11.213.216", "47.11.239.230", "30"

I'm just about out of ideas
Hope this helps -


TGD

 

[mshahrukhali101]

I will update you tomorrow on this, if it's work.