9620 No Signalling 2011 1

[Avayell]

Hello,
I have a problem with an 9620 in a remote location. The server is an S8400. The phone seems to be registered. The problem is that although it is registered, most of the times it does not work. You can see the trace bellow. Strange thing is that when i plug in a 4610 it works like a charm. Another thing to mention is the message i see on the 9620 when the problem appears. "No Signalling 2011". I searched for that and i found out that it is about a forced unregistration request. What should i do? And why it happens only with 9620? Also upgraded the 9620 but nothing.
Any help much appreciated.


11:12:26 Calling party trunk-group 3 member 14 cid 0x5c
11:12:26 Calling Number & Name NO-CPNumber NO-CPName
11:12:26 dial 030
11:12:26 term station 030 cid 0x5c
11:12:26 idle trunk-group 3 cid 0x5c
11:12:32 denial event 2011: IP FURQ-No Q931 msg rcvd
endpt 192.168.93.10 data0:0x66
11:12:32 snd URQ ext 030
endpt [192.168.93.10]:49305
switch [... ... ... ...]:1719
11:12:38 rcv GRQ ext 030
endpt [192.168.93.10]:49306
switch [... ... ... ...]:1719
11:12:38 snd GCF ext 030
endpt [192.168.93.10]:49306
switch [... ... ... ...]:1719
11:12:38 rcv RRQ ext 030
endpt [192.168.93.10]:49306
switch [... ... ... ...]:1719
11:12:38 snd RCF ext 030
endpt [192.168.93.10]:49306
switch []:1719
11:12:38 TCP connected (fe)
endpt [192.168.93.10]:8553
switch [... ... ... ...]:1720
11:13:38 denial event 2011: IP FURQ-No Q931 msg rcvd
endpt 192.168.93.10 data0:0x66
11:13:38 snd URQ ext 030
endpt [192.168.93.10]:49306
switch [... ... ... ...]:1719
11:13:43 rcv GRQ ext 030

 

[Nick44]

What firmware are you running on the 96xx?


Speak softly and carry a big switch

 

[Avayell]

It was in 3.0 and now it is in 3.1

 

[Gibsonic]

the clue is the message "denial event 2011: IP FURQ-No Q931 msg rcvd"

what is the trunking between the CM and this remote phone?

ipsec vpn tunnel by chance? what types of ACL's are in place for UDP port ranges?

 

[kpearlt3]

You should look at the traffic going form your CLAN to your remote phone to start. What usually happens is the phone will do its registration using UDP 1719 on the CLAN side and that's the first half and the second half is there is a TCP socket that is established between the CLAN and the phone if this is successful you'll get your date and time and the display get's updated on your phone. That denial event states that Communication Manager is not receiving that message during the phones registration. When the phone appears to be "Registered" before you make a call what state does the station appear to be in and does that look the same as a 9600 phone that is not at the remote site.

 

[Avayell]

Thanks for the responses,

I did not manage to get the details, but the really curious thing is that all other phones(46xx,16xx) in that NR are working fine. Are there any differencies in the registration process or in the signalling between 46xxs and 96xxs?
I will come back with the routers configurations.

 

[Nick44]

When you updated the 9600 to 3.1 did you make sure you used the correct version? h.323 / SIP?


Speak softly and carry a big switch

 

[Avayell]

I am sure i supplied the h.323 firmware

 

[Nick44]

I had a similar issue with 9620 failing to register, but in my case it was when using the hot desk login/out feature.

As you are not having problems with 46xx, it must be something to do with the 96xx. Have you tried backing down the firmware to an earlier version, say 2 or 1.5?

Speak softly and carry a big switch

 

[Nick44]

I have just been told by Avaya that there is a new 46xxsettings.txt file to go with firmware ver 3.1
Get it from

https://support.avay.com

Has loads of new fields in t.

Speak softly and carry a big switch

 

[Avayell]

Happy New Year to everyone.
The problem is turning out to be really weird. I have tried with 1616, 4610, 1608, 4602 and there was no problem. But when i tried with 9640,9620 and 9650 , i faced the problem with the 2011 no signaling.
What is the difference between 9600 and all the other series?

 

[billybobdan]

I have had the same issue, all other phone types worked okay but 96xx phones failed with the 2011 error. The solution was in the firewall settings on the local firewall. (a cisco device). The ports had to be implicitly opened. The setting that was causing the issue was set to allow all ports through the firewall, but the cisco did not allow H323 to pass until we allowed the ports 1719 and 1720.

Test this by disabling the firewall entirely.

It would appear that the 96xx has slightly different registration sequence to the other phones (very weird).

Good luck, this took me 3 days to find the cause.

 

[Avayell]

Your suggestion solved my case Billybobdan. Thank you very much. A Big Big Star for you, and also my wishes for a Happy New Year.