SRG 1.0 / BCM 200 3.7 1

[subx]

Hi there... Im try to set up a BCM 200 3.7 as SRG 1.0
but i guess im doing something wrong.... Anybody has a "how to" description in short ways how to set it up?!?
I did already enter SRG Keycode, Reboot, Quick Install Wizard, Reboot, MBM Installation, SRG Update Wizard, Reboot...
Setting up NRS ( just Standard and a Endpoint )

Now i did register 2 Phones on SRG.. they run fine in local mode but they cant register on MO... On SigServ i get following ERROR "07/03/2006 17:39:57 LOG0005 GKNPM: RAS FAILURE: RAS_TYPE : GRQ,Reason=terminalEx
cluded,SrcIP=10.118.19.111:1139"
on SRG i get Invalid ID (1) No Endpoint in Gatekeeper Database... so any hints? I did set a endpoint with SRG-IP already...So whats missing?

regards,

subx

 

[biv343]

Is the SRG registered to the NRS/Gatekeeper? Which release is the main office running? Is NCS enabled on the NRS (it needs to be if release 4.5)?

The phones are built on the main office, correct?

Sounds to me like the incorrect IP address has been entered for the main office and it's trying to register to an IP other than the node IP.

 

[subx]

hi biv ;O)

thx for ur response so far... MO is running Release 4.5... NCS is enabled on both SRG Endpoints... but that already work... i did forgot to set up an own Location in NRS for MO... anyways i still have problems about that...
The endpoints dont register ... h323 or sip both dont register on NRS ... even i did set up 2 SRG endpoints there... i always get
08/03/2006 10:12:06 LOG0005 GKNPM: RAS FAILURE: RAS_TYPE : GRQ,Reason=terminalEx
cluded,SrcIP=10.118.19.111:1139
08/03/2006 10:12:13 LOG0003 NPM: cmEvRASTimeout: GK 10.118.20.60 Registration ti
meout
08/03/2006 10:12:16 LOG0005 GKNPM: RAS FAILURE: RAS_TYPE : GRQ,Reason=terminalEx
cluded,SrcIP=10.118.19.111:1139
08/03/2006 10:12:26 LOG0005 GKNPM: RAS FAILURE: RAS_TYPE : GRQ,Reason=terminalEx
cluded,SrcIP=10.118.19.111:1139
08/03/2006 10:12:26 LOG0003 SIPNPM: ITG2107 Proxy Server / Redirect Server <10.1
18.20.60:5060> unreachable (7)
08/03/2006 10:12:26 LOG0004 SIPNPM: sipNpmKeepAliveResTimerEv: Primary proxy <10
.118.20.60:5060> lost for 3 times...
08/03/2006 10:12:26 LOG0004 SIPNPM: sipNpmProxyAddrSwap: Secondary Proxy <0.0.0.
0:5060>invalid state try failsafe
08/03/2006 10:12:26 LOG0004 SIPNPM: sipNpmProxyAddrSwap: failsafe proxy not conf
igure
08/03/2006 10:12:36 LOG0005 GKNPM: RAS FAILURE: RAS_TYPE : GRQ,Reason=terminalEx
cluded,SrcIP=10.118.19.111:1139
08/03/2006 10:12:38 LOG0003 NPM: cmEvRASTimeout: GK 10.118.20.60 Registration ti
meout

regards,
subx

 

[biv343]

Under the alias name in the H.323 trunk field on the SRG, did you put in NAME:endpointname? NAME: must precede the endpoint name and must be in capital letters.

Call Signalling - gatekeeper resolved

Primary gatekeeper IP - sig server node address

Protocol - CSE

Under the SRG parameters, the H.323 ID needs to match the endpoint name in NRS, but doesn't need the NAME: preceding it.

Also, don't forget the node ID under the SRG parameters, and the zone/VPNI information in the SRG (under general settings, IP Trunking).

 

[subx]

ok... thx about that.. i noticed it had problems if ur using the fixed IP also...

Anyways the problem is resolved but here comes the next question...

People who are on the SRG Location should use local PSTN for outdialing and they should also be able to get calls over that PSTN while they are in "normal" mode...

maybe anybody give me a step by step soloution how to set this up in MO and SRG?!?

regards,

subx

 

[biv343]

Kind of hard to summarize that here, but this is the "quick version" of what needs to be done:

1. Configure remote access packages so the IP trunks have access to the PSTN trunks on the SRG and vice versa.
2. To make a analog line or target line ring on the main office phone, simply assign the line to the local mode DN on the SRG. When the phone is redirected in normal mode, the lines will forward to the MOTN and the phone will ring.

3. Outdialing via local PSTN trunks on SRG from a normal mode set. Each SRG site needs to be in a specific zone. That zone needs to have ZRBN support enabled. Under zone dialing plan/access codes, set prefix ACB_DC1 to a unique number. You'll attach this to calls going out of the main office. Set dialed access code to AC1, new access code to AC2. In the ZESA config, set your ESA route, and prepend digits.

Lets say your prepend digits are 123. You'll need to define 1231, 1232, 1233, etc as publicnumber.international number in the NRS against the SRG H.323 endpoint. You then build SPN's in the PBX against those numbers (LD 90, FEAT, NET, AC2, SPN, 1231 2, FLEN 14, RLI XX), so on and so forth until you've built all the possible combinations.

On the SRG, build a destination code of 123, strip all digits, and point to the route that contains the PSTN trunks.

At this point, you're ready to turn on D-channel messaging and the BCM monitor and fine tune things.

I may have missed a step or two, but this should get you well on your way.

 

[subx]

thx biv again.. i will try that tomorrow..receiving seems easy but outgoing sounds complicated... i will have a try later...

regards,

subx

 

[subx]

I'm still on my way to set up SRG :O(

Now i got the things until that......

IP Phones work in local and normal mode... i can make H323 calls from CS1000 to SRG (local mode) but if i try to make calls from SRG to MO i get the following Error

DCH 25 IMSG SETUP REF 00008181 CH 66 0 0 0 TOD 14:14:10
CALLING #:300 NUM PLAN: PRIVATE/ABBREVIATED (CDP)
CALLED #:331 NUM PLAN: PRIVATE/ABBREVIATED (CDP)

DCH 25 OMSG REL COMP REF 00008181 CH 66 0 0 0 TOD 14:14:10
CAUSE :SWED EQIP CONGESTION
DIAG: 171


Thats a trace from CS1000 i get the same on BCM Monitor

Anybody know what exactly that means? If the user i try to reach is not on the system and if the user is busy i get already the right traces... but if user should get the call i just get the error and on IP Phone in local mode its something like Network busy......

regards,

subx