Webswitch 2000 (EEBG)

[djudjuman]

Is their anyone who has knowledge about the EEBG. ?
If so, I would like to post a question.

Tnx.

 

[fidde]

Sure go on.

 

[djudjuman]

I want to register two H.232 extensions in the EEBG. I have added them via NetManager. The 2 phones (Dialog 3413) have IP 200.100.100.2 and 200.100.100.3
The EEBG has IP 200.100.100.100
I configured a gatekeeper (I suppose I have to do that) with IP 200.100.100.200 via NetManager.
The IP phones are loaded with config file for Webswitch3. The gatekeeper address in the phones are 200.100.100.200
However the phones can't register in the EEBG. They can't find the gatekeeper. I can ping all address, but not the address for the gatekeeper (200.100.100.200)



VxWorks login: ipphone
Password:

->
-> 70-01-01 21:25:20.790 Watch: WatchTask: Wrong NTP get message!
70-01-01 21:25:32.570 UserInt: TIMEOUT msg rec, Data=20
70-01-01 21:25:32.570 UserInt: UI state changed: uiWaitLogOn
70-01-01 21:25:32.570 UserInt: LOGON REQUEST msg sent to H323, Number=2400 Pas
70-01-01 21:25:32.570 UserInt: word=
70-01-01 21:25:32.570 keyRead: rec LOGONREQ_MSG,key
70-01-01 21:25:32.570 keyRead: ***(RRQ)->***ChId:0
70-01-01 21:25:32.570 keyRead: Using GK addr from netSett:200.100.100.200
70-01-01 21:25:38.580 resendRRQo: ***************resend RRQ or RRQ Per. timeou
70-01-01 21:25:38.580 resendRRQo: ****************
70-01-01 21:25:38.580 resendRRQo: ***(RRQ)->***ChId:0
70-01-01 21:25:38.580 resendRRQo: Using GK addr from netSett:200.100.100.200
70-01-01 21:25:44.590 resendRRQo: ***************resend RRQ or RRQ Per. timeou
70-01-01 21:25:44.590 resendRRQo: ****************
70-01-01 21:25:44.590 resendRRQo: ***(RRQ)->***ChId:0
70-01-01 21:25:44.590 resendRRQo: Using GK addr from netSett:200.100.100.200
70-01-01 21:25:50.600 resendRRQo: TotalTimeout RRQ or RRQPER
70-01-01 21:25:50.600 keyRead: recv 't',key
70-01-01 21:25:50.600 keyRead: timeout to UI
70-01-01 21:25:50.600 keyRead: KeyRead Waiting for Logon from the UI(level 2)
70-01-01 21:25:50.600 UserInt: LOGON REJECT msg rec, Reason=0 Data=0
70-01-01 21:25:50.600 UserInt: UI state changed: uiLogOn
70-01-01 21:26:20.610 UserInt: TIMEOUT msg rec, Data=20
70-01-01 21:26:20.610 UserInt: UI state changed: uiWaitLogOn
70-01-01 21:26:20.610 UserInt: LOGON REQUEST msg sent to H323, Number=2400 Pas
70-01-01 21:26:20.610 UserInt: word=
70-01-01 21:26:20.610 keyRead: rec LOGONREQ_MSG,key
70-01-01 21:26:20.610 keyRead: ***(RRQ)->***ChId:0
70-01-01 21:26:20.610 keyRead: Using GK addr from netSett:200.100.100.200
70-01-01 21:26:26.620 resendRRQo: ***************resend RRQ or RRQ Per. timeou
70-01-01 21:26:26.620 resendRRQo: ****************
70-01-01 21:26:26.620 resendRRQo: ***(RRQ)->***ChId:0
70-01-01 21:26:26.620 resendRRQo: Using GK addr from netSett:200.100.100.200
70-01-01 21:26:32.630 resendRRQo: ***************resend RRQ or RRQ Per. timeou
70-01-01 21:26:32.630 resendRRQo: ****************
70-01-01 21:26:32.630 resendRRQo: ***(RRQ)->***ChId:0
70-01-01 21:26:32.630 resendRRQo: Using GK addr from netSett:200.100.100.200
70-01-01 21:26:34.790 Watch: WatchTask: Wrong NTP get message!
70-01-01 21:26:38.640 resendRRQo: TotalTimeout RRQ or RRQPER
70-01-01 21:26:38.640 keyRead: recv 't',key
70-01-01 21:26:38.640 keyRead: timeout to UI
70-01-01 21:26:38.640 keyRead: KeyRead Waiting for Logon from the UI(level 2)
70-01-01 21:26:38.640 UserInt: LOGON REJECT msg rec, Reason=0 Data=0
70-01-01 21:26:38.640 UserInt: UI state changed: uiLogOn

The manual doesn't tell me anything about programming a gatekeeper for adding H.323 extensions.

I have made some screen dumps, but unfortunately I can't attach them.

I am certainly missing something.

Tnx

 

[fidde]

You do not have to add a GK this is to define a external GK as cisco CCM. The EEBG has it's own built in GK so if you change the GK ip to 200.100.100.100 it will work if everyting else is ok.

Fredrik

 

[djudjuman]

To FIDDE:

No gatekeeper is excactly what I tried in the first place.
So I deleted gatekeeper address 200.100.100.200

My IPphone (extension 2400) Network settings are programmed as follows:
DHCP=NO
IP=200.100.100.2
Subnet Mask=255.255.255.0
Default gateway=200.100.100.11

http://WWW server

from DHCP=NO

http://WWW server=200.100.100.11

(same as default gateway, because I use a PC as a router in the lab)

http://WWW proxy=NO

Gatekeeper discovery=Default(NO)
Gatekeeper=200.100.100.100 (my EEBG !!)
Password=NO

On my phone is written: Enter extension number:2400
When I press the logon key: NO REACTION AT ALL !! So I can't logon.
This problem I had from the beginning. That's why I tried to program a gatekeeper address in the EEBG.
At least the phone was trying to logon, but also failed.

So their is still something which is not ok.



70-01-01 1:17:49.530 UserInt: TIMEOUT msg rec, Data=20
70-01-01 1:17:49.530 UserInt: UI state changed: uiWaitLogOn
70-01-01 1:17:49.530 UserInt: LOGON REQUEST msg sent to H323, Number=2400 Pass
70-01-01 1:17:49.530 UserInt: word=
70-01-01 1:17:49.530 keyRead: rec LOGONREQ_MSG,key
70-01-01 1:17:49.530 keyRead: ***(RRQ)->***ChId:0
70-01-01 1:17:49.530 keyRead: Using GK addr from netSett:200.100.100.100
70-01-01 1:17:49.570 rasRec: ***<-(RRJ)***
70-01-01 1:17:49.580 rasRec: stopResendRRQorRRQPER_Q Sent
70-01-01 1:17:49.580 rasRec: invalidAlias
70-01-01 1:17:49.580 keyRead: recBuff:r rrj reason,25func:11
70-01-01 1:17:49.580 keyRead: 1LOGON_REJECT or timeout
70-01-01 1:17:49.580 keyRead: KeyRead Waiting for Logon from the UI(level 2)
70-01-01 1:17:49.580 UserInt: LOGON REJECT msg rec, Reason=2 Data=0
70-01-01 1:17:49.580 UserInt: UI state changed: uiLogOn
70-01-01 1:17:49.590 resendRRQo: rec dummy msg
70-01-01 1:17:54.750 Watch: WatchTask: Wrong NTP get message!
70-01-01 1:18:19.590 UserInt: TIMEOUT msg rec, Data=20
70-01-01 1:18:19.590 UserInt: UI state changed: uiWaitLogOn
70-01-01 1:18:19.590 UserInt: LOGON REQUEST msg sent to H323, Number=2400 Pass
70-01-01 1:18:19.590 UserInt: word=
70-01-01 1:18:19.590 keyRead: rec LOGONREQ_MSG,key
70-01-01 1:18:19.590 keyRead: ***(RRQ)->***ChId:0
70-01-01 1:18:19.590 keyRead: Using GK addr from netSett:200.100.100.100
70-01-01 1:18:19.630 rasRec: ***<-(RRJ)***
70-01-01 1:18:19.640 rasRec: stopResendRRQorRRQPER_Q Sent
70-01-01 1:18:19.640 rasRec: invalidAlias
70-01-01 1:18:19.640 keyRead: recBuff:r rrj reason,25func:11
70-01-01 1:18:19.640 keyRead: 1LOGON_REJECT or timeout
70-01-01 1:18:19.640 keyRead: KeyRead Waiting for Logon from the UI(level 2)
70-01-01 1:18:19.640 UserInt: LOGON REJECT msg rec, Reason=2 Data=0
70-01-01 1:18:19.640 UserInt: UI state changed: uiLogOn
70-01-01 1:18:19.650 resendRRQo: rec dummy msg
70-01-01 1:18:49.650 UserInt: TIMEOUT msg rec, Data=20
70-01-01 1:18:49.650 UserInt: UI state changed: uiWaitLogOn
70-01-01 1:18:49.650 UserInt: LOGON REQUEST msg sent to H323, Number=2400 Pass
70-01-01 1:18:49.650 UserInt: word=
70-01-01 1:18:49.650 keyRead: rec LOGONREQ_MSG,key
70-01-01 1:18:49.650 keyRead: ***(RRQ)->***ChId:0
70-01-01 1:18:49.650 keyRead: Using GK addr from netSett:200.100.100.100
70-01-01 1:18:49.690 rasRec: ***<-(RRJ)***
70-01-01 1:18:49.700 rasRec: stopResendRRQorRRQPER_Q Sent
70-01-01 1:18:49.700 rasRec: invalidAlias
70-01-01 1:18:49.700 keyRead: recBuff:r rrj reason,25func:11
70-01-01 1:18:49.700 keyRead: 1LOGON_REJECT or timeout
70-01-01 1:18:49.700 keyRead: KeyRead Waiting for Logon from the UI(level 2)
70-01-01 1:18:49.700 UserInt: LOGON REJECT msg rec, Reason=2 Data=0
70-01-01 1:18:49.700 UserInt: UI state changed: uiLogOn
70-01-01 1:18:49.710 resendRRQo: rec dummy msg

 

[fidde]

Now at least you get the RRJ registration reject. I think it's beacuse of the alias (password). Under the H323 extension enable "Use password authentication" (if it's not) then enable the password on the IP-phone and use "555" as password (that is the default in EEBG).

I have had that problem with other H323 devices.

Let me know how it goes.
Fredrik

 

[mikka631]

Two things you should check;

1. Is the config file for the ip phone set for the right system (webswitch).

2. Is the phone actually downloading this config file. You can check this by logging into the phone and entering d x 053f0000,4600.

 

[djudjuman]

To cstmp

My IP phone is set for System=WEBSWITCH3. (which is version 3 or higher). I am using version 3.1.3.

 

[djudjuman]

If the Ipphone is registered in the MD110 and in survivebility mode the phone re-registers in the EEBG the System parameter in the phone will still be on MD110.??

This means that it should be possible to register in the EEBG with System=MD110.

Am I correct or ....

I have tried to register in the EEBG with system parameter as MD110 and as Webswitch3. In both cases I can't logon.

 

[ETBOY]

Hi,
In DBC4425 in config file you have:
System=Md110
PrimaryGatekeeper=
.
.
.
[BackupGatekeeper]
system=webswitch3
ipaddress=....

In normal mode ip phone is registed in MD110 and in survive mode ip phone re-registers in EEBG.
So if you have only EEBG your SYSTEM must be Webswitch3.
what software version of ip phone do you have?
you have 3.1.3 version in EEBG, what build? 7 is the latest.
If you have choose password authentication in extension,unselect this option or if want a password in ip phone, change password to yes in ip phone and then try 5555
that is the default password for voice mail. when you log in in ip phone dial *0 to enter in voice mail and then change the password.
In past i have used DBC3412 and i don't have problems.

BR,

 

[djudjuman]

I have tried to log on with password option in my phone set to YES, and in NetManager: Use Password Authentication ticked.
On the display of my phone:
Enter extension number: 2400
Enter password: 555 (I also tried 5555)

After pressing the logon button, the phones replies immediately with:
Enter extension number:...

The problem is that it is not finding 200.100.100.100

If I use Microsoft Netmeeting to logon to the EEBG I get the error message:
"Connection to gatekeeper refused."
Logging on with Netmeeting in the MD110 is no problem.

TELNET session to Webswitch printout:

WebSwitch (200.100.100.100)

Copyright (c) Ericsson WebCom Inc., 1999-2001.
Welcome to the WebSwitch

Do not access the WebSwitch until it is in READY(Normal) state.
Use <devstate> to check the state of the WebSwitch.

Password:
Password accepted
ws>ver
Release label = WS2000_03.12.B13(CPU2) DATE(y-m-d): 2003-5-23, TIME(h:m): 10:01

Bootcode version = BOOTCPU2_02.00.B05 DATE(y-m-d): 2001-12-12, TIME(h:m): 17:58

I am using software version 3.1.3

That a simple thing can be so difficult !!

 

[ETBOY]

Hi,

In webswitch you have:
Release label = WS2000_03.12.B13(CPU2) DATE(y-m-d): 2003-5-23, TIME(h:m): 10:01

So this is version 3.1.2 build 13!
If in bottom of your netmanger says 3.1.3 build ...
you have to go to menu file in netmaneger and choose upgrade webswitch.Because this mismatch could give problems.
Check netmask in webswitch and in ip phone.
Telnet to ws>setip


Can you put in forum your ip-phone config file.
BR,

 

[djudjuman]

In the bottom of my NetManager I have:
Software 3.1.3 (build 4)

 

[mdfan]

You say that even netmeeting cant see the GK.
Perhaps a silly question but after having changed the configuration data like IP address etc did you reset the EEBG ?

From ALEX :

Termination
The following steps shall be followed when the configuration of the EEBG and / or ITG have been altered:

Download the configuration to the EEBG and / or ITG via the Net Manager.
Do a reset of the EEBG and / or ITG

 

[fidde]

Ok, the problem is that your netmanager version is newer than you WS. I do not think that there are any extensions in it. You first need to do a upgrade from netmanager and then send the configuration again. The version of netmanager needs to correspond to the version of WS.

Try that. You can also check you h323 extension from the command promt. "h323 all" gives the extension. I would guess it's "empty".

Fredrik

 

[djudjuman]

You are correct FIDDE. My netmanager is newer than my EEBG cinfig.
I did not notice that until you pointed it out.
I will do an upgrade today.

I will let you know my result later.

(duvel: how are you ? did you get what you needed ??)

TNX

 

[djudjuman]

IT IS WORKING NOW !!!!!!
=========================

Special thanks to ETBOY and FIDDE, who brought me on the right track.
The software version in the EEBG and in NetManager had a mismatch. After I upgraded the EEBG everything worked at once. Even before I could have a look at the phone, it had already logged in.
Of course also thanks to everybody else who contributed to the solution.

TNX.