GeoRedun and Invalid ID (1) on phone

[dgrizzard]

First I have two sites both running rls 5.5, second site is still in the implementation phase hence the problems. The phones at the branch office site register locally but then on the phone it says "Invalid ID (1)". After some digging I found out that means either an invalid user ID or the user ID is not found on the gatekeeper. Unfortunately I haven't found in my system yet where I've screwed up.

I will lay out what I have done so far and please let me know if I've missed something, or done something incorrectly.

Primary and secondary call servers have been setup for geo redun. 

Separate node setup at second site pointing to the primary NRS at the main site. 

Gateway endpoints are setup for both locations with NCS checked

Routing entries setup for both locations, with route cost of 1 setup for the main site. Branch office site uses 62XX DN range, so a route of 62 with cost of 1 at the main endpoint and cost of 2 for the branch office endpoint.

HLOC setup on both call servers (not sure if this is right?)

Zone setup is pretty standard, BQ on both inter/intra and no Branch Office settings

Besides the error on the phone I am getting the following error on the NRS console

07/10/2009 10:17:45 LOG0004 NCSSend: ncsMsgProcess : src=FOI_GR_SS DN not found: 6234

I have verified that the routing entries are correct on the NRS for both endpoints, and the DN does exist on both call servers.

If anyone has some clue as to what I'm doing wrong, or at least where I should be looking at I would be extremely grateful.

TIA

 

[biv343]

Do you have your HLOC number added in the NRS as a UDP entry against the main office endpoint?

 

[dgrizzard]

First, should I have the HLOC (1200) setup as the HLOC on both call servers? Also, will it matter if it is AC1 or AC2 (we only use AC1)? Should I also put it in a DMI that strips off the 4 digits (I currently do)?


To answer your question I do have the HLOC setup as a udp routing entry against the main office with a route cost of 1.

 

[Tman45]

Can you print out your phone builds for x6234 please?

 

[dgrizzard]

Here it is...thanks again for all the help...

Branch office

REQ: prt
TYPE: 2002p1
TN   100 0 2 21
DATE
PAGE
DES
MODEL_NAME
EMULATED
KEM_RANGE

DES  6703
TN   100 0 02 21  VIRTUAL
TYPE 2002P1
CDEN 8D
CTYP XDLC
CUST 0
NUID
NHTN
CFG_ZONE 006
CUR_ZONE 006
ERL  261
ECL  0
FDN  6000
TGAR 1
LDN  NO
NCOS 5
SGRP 0
RNPG 0
SCI  0
SSU  0005
LNRS 16
XLST
CLS  CTD FBD WTA LPR MTD FNA HTA TDD HFA CRPD
     MWA LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
     POD DSX VMD SLKD CCSD SWD LNA CNDA
     CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
     ICDD CDMA LLCN MCTD CLBD AUTU
     GPUD DPUD DNDA CFXD ARHD CLTD ASCD
     CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD AHD
     DDGA NAMA
     DRDD EXR0
     USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
     VOLA VOUA CDMR ICRD MCDD T87D KEM2 MSNV FRA  PKCH
CPND_LANG ENG
RCO  2
HUNT 6000
LHK  1
PLEV 02
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY  00 SCR 6234 0     MARP
     01
     02
     03
     04
     05
     06
     07
     08
     09
     10
     11
     12
     13
     14
     15
     16 MWK 6000
     17 TRN
     18 AO6
     19 CFW 16
     20 RGA
     21 PRK
     22 RNP
     23
     24 PRS
     25 CHG
     26 CPN
     27
     28
     29
     30
     31

Main office

REQ: prt
TYPE: 2002p1


TN   100 0 2 21
DATE
PAGE
DES
MODEL_NAME
EMULATED
KEM_RANGE

DES  6703
TN   100 0 02 21  VIRTUAL
TYPE 2002P1
CDEN 8D
CTYP XDLC
CUST 0
NUID
NHTN
CFG_ZONE 006
CUR_ZONE 006
ERL  261
ECL  0
FDN  6000
TGAR 1
LDN  NO
NCOS 5
SGRP 0
RNPG 0
SCI  0
SSU  0005
LNRS 16
XLST
CLS  CTD FBD WTA LPR MTD FNA HTA TDD HFA CRPD
     MWA LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
     POD DSX VMD SLKD CCSD SWD LNA CNDA
     CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
     ICDD CDMA LLCN MCTD CLBD AUTU
     GPUD DPUD DNDA CFXD ARHD CLTD ASCD
     CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD AHD
     DDGA NAMA
     DRDD EXR0
     USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
     VOLA VOUA CDMR ICRD MCDD T87D KEM2 MSNV FRA  PKCH
CPND_LANG ENG
RCO  2
HUNT 6000
LHK  1
PLEV 02
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY  00 SCR 6234 0     MARP
     01
     02
     03
     04
     05
     06
     07
     08
     09
     10
     11
     12
     13
     14
     15
     16 MWK 6000
     17 TRN
     18 AO6
     19 CFW 16
     20 RGA
     21 PRK
     22 RNP
     23
     24 PRS
     25 CHG
     26 CPN
     27
     28
     29
     30
     31

 

[dgrizzard]

Just wanted to update with more information, I also have separate nodes for each location as well. Not sure if this will impact it or not. Setup as... main office 1001 and branch is 1003, the phone is programmed for node 100 so it will pick up either.

 

[dgrizzard]

Update: after reading the system redundancy NTP, I've got both main office and branch setup with the same Node ID and the same HLOC. The routing is still the same with the HLOC(1200) having a route of 1 on the main and 2 on the branch, the DN(6234) is setup for CDP 62 and route of 1 to main and 2 to the branch.

I do have a DMI of del 4 and no change setup for the HLOC on both, but I've changed this to del 0 and CDP for the CTYP...made no difference though.

Anyone have an SMG setup that could provide some insight?

Thanks in advance

 

[Tman45]

Actually, you know what? I think this could be an issue because your phone is a 2002 P1 (is your phone really a Phase 1 phone?) - check the back - I believe some others on this forum posted something about invalid ID or something and it had to do with Phase 1 compatibility. Is it actually causing a problem with the phone functionality?
If your site is pretty stable and the phone doesn't need to 'failover' per se you can just put it on one node and leave it at that

 

[dgrizzard]

Yeah it really is a phase 1, but I tried a phase 2 just now with the same result.

Besides the phone saying invalid id 1, the MGC is set to register to the main call server so I can't make TDM calls.

I guess the thing I keep coming back to is the DN not found error message coming from the NRS. Just doesn't make any sense.

 

[dgrizzard]

Someone tell me this is not how it is suppose to work...

I went back and entered 6234 for the NUID on the branch office CS and it worked. I thought it was suppose to automatically create the NUIDs based on ac1/2+hloc+dn?

 

[Tman45]

Yea you know what? I was going to ask you to maybe enter a NUID ... we didn't have NUID set on our current setup - so I didn't think that was the issue, but we did have a CS1000S and Branch where the BUID had to be set on the branch. Could be the way your Geo is setup - not sure - someone else will have to verify.