Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CS1000 Rel 5 & SRG 50 v2 - Using UDP network.

Status
Not open for further replies.

sl1input

Technical User
Apr 17, 2006
233
GB
Hi,

I am having issues redirecting IP sets from my SRG to the Main Office CS1000, using a UDP network.
I have installed many SRG's using CDP with no problems.
When the set is in local mode, i fill the MOTN & BUID info in the SRG, when i click "redirect set" the set will show "locating server" after a few seconds i will see "Terminal Manager Connect" the set will then flash the Red Message Lamp and return into local mode.

If i log into the Main Office Sig Server Node (telnet), i see the attempted registration in the shell appear.
I see (example):
LOG Terminal 000-0-00-00
LOG Connect ID x669320
LOG Terminal Offline

In the SRG, registration status is "invalid ID (2) ID unknown with call server".

I know that the set is hitting the Main Office node and routing correctly via NRS, but the CS can't seem to identify the set.

If i change to CDP routing the set connects fine to CS via SRG.

My config is:

RAS H323 endpoints with NCS enabled.
BUID in SRG 84165200 (8 = Voip Trunk access code, 416 Main Office site code, 5200 DN in CS).
Level 1 (UDP) routing entry of 416 at Main Office.
Destination code of 8 pointed at VOIP pool bloc A, absorb all.
Remote access package on Voip trunks.
MOTN as in Main Office (same phone type configured).
MO access code length = 1.
Network type = ESN UDP & Private
PNI and VPNI = 1 at both sites.
Main office 416 = LSC with DEL 3.

Like i said this works with the above settings except using CDP not UDP. Im pretty sure all the SRG config is right as if any parameter is incorrect when i click redirect the set will not even attempt to locate server and will sit in local mode.

Thanks

 

I've encounterd this exact problem which turned out to be programming on the SRG end (at least in my case). From your notes:

In the SRG under the MO Coniguration Tab: For UDP, the MO Access Code length should be the length of the access code + LOC.

VoIP Trunk Access Code is for CDP only. Change to none for UDP Config. The BUID does the job for UDP.

If that does not take care of the issue, can you please advise if the error code changes? I'm still thinking about this as it has been a while since I've worked on the UDP config on SRG.




 
taking the SRG out of the equation when you set the S1 address of the phone to the MO does the phone register?
 
Thanks r307

I think your on the right path.

When you say MO Access code should be access code + LOC, which access code do you refer to. Do you mean desination code, as i don't need the VOIP Access code right?

My setup is LOC 416 DN 5200

So i will change BUID to = 4165200 currently 84165200

If access code being destination code of 8 then MO Access Code Length will be 4.


kungfumstr

Yes my set registers direct to MO no issues. It also registers via SRG using CDP no issues either.
 

Close but if I recall correctly -

Under the MO config tab, removed the 8 from the VoIP Trunk access code.

MO Access code length - 4

Keep the dest code of 8

BUID: I believe you have to keep the 8: 84165200

I'm a tad rusty on this config and have no way to test it but the above is what I'd try.

 
Thanks r307

I have removed VOIP Trunk Access Code.

However when you highlight the box it say that VOIP Trunk Access Code is for UDP only and to ignore for CDP??

When i removed the VOIP access code iget the same as before.

When i change access code length to 4, the set does nt attempt to register. I have tried 1,2,3,4 only when set to 1 will the set attempt to connect.

I see the following on SS shell, when the set attempts registration:

oam> 22/04/2008 16:49:23 LOG0006 SET: 192.168.10.10 TN 000-00-00-00 Terminal offline
22/04/2008 16:49:23 LOG0005 VTM: 192.168.10.10 Unregistered, terminal = 0x2e0fddac, device = 0x2e2361fc
22/04/2008 16:49:23 LOG0006 VTM: vtmUSIBootHandler: SET is Security Capable
22/04/2008 16:49:23 LOG0006 VTM: ITS5008 Terminal connection status: ok IP=192.168.10.10:5000, HWID=18001daffe11076623 (20)

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top