Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

IP/VC 3520 configuration help!

Has anyone configured polycom viavideo(LAN based h323 clients) talking through IP/VC 3520

gateway onto WAN h320 nodes

Present scenario : IPVc 3520 LAN gatewayip is 192.168.20.58 WAN side only one BRI

connected and assigned a numberISDN

gateway configured to use embedded gatekeeper

gatekeeper pemanent zone file entries mapping ip to extension numbers

Callrouting inwards tcs4

Polycom viavideo clients configured to use gatekeeper and H323 extension which

matches extension numbers in zone file of gatekeeper

STill cant get this thing to work...initially when we had automatic registration we got errorr"duplicate aliases in Gatekeeper"..we have removed the same now and manually entered h323 lan endpoints in the zone table of gatekeeper..now it registers but "service not found "

Can anyone define

the exact workflow of a call being placed from LAN to WAN and viceversa

When WAN places a LAN call...is it the gatekeeper that routes the call inward??

I have defined TCs4 inward

regards

6 REPLIES
Cisco Employee

Re: IP/VC 3520 configuration help!

You should kill your configuration and start from scratch.

1. enable the embedded GK

2. Configure the gateway to registerer with embedded GK address (same address used for the gateway)

3. Configure a service prefix for outbound calls (example 9) to dial outbound you will dial 91<10-digit ISDN number(s)>

4. Enable IVR only on the gateway for inbound call routing (this allows you to test and verify that the gateway is answering the inbound calls correctly)

5. Configure H.323 extension on your Via Video (example 55555)

6. Configure Gatekeeper address on the Via Video (gateway IP address)

Reboot gateway and client. Make sure the gateway and endpoint are listed in the gatekeeper registrations (do not hard code anything). Also make sure that the gateway service prefix is listed in the service table.

7. Go to the Via Video and try dialing out using the service prefix and ISND number(s).

8. Dial inbound to the gateway from ISDN (you should get the IVR) after the IVR answers enter the Via Video's h.323 extension (55555) followed by the # sign.

This should get you started.....

New Member

Re: IP/VC 3520 configuration help!

Hi,

2. Configure the gateway to registerer with embedded GK address (same address used for the gateway)

Do i do the above by manually defining a gateway in the gatekeeper zone table

or

Do i just enable automatic registration in gatekeeper network properties

2)Make sure the gateway and endpoint are listed in the gatekeeper registrations (do not hard code anything).

DO not hard code anything---do you mean i enable automatic registration..ie DO NOT PERMANENTLY and manually define endpoints terminal.gateway in the gatekeeper zone file

What is wrong when we use TCs4 inbound routing and manuall populate the gatekeepers zone file

One last thing what port no should we enter in the treminal settings in the zone table of the gatekeeper

. Dial inbound to the gateway from ISDN (you should get the IVR) after the IVR answers enter the Via Video's h.323 extension (55555) followed by the # sign.

>>>>>is it followed or preceded by #

Regards and thanks

Cisco Employee

Re: IP/VC 3520 configuration help!

You shouldn't manually configure any endpoint information in the Gatekeper. In the gateway configuration you will enter its own IP address.

You should have all endpoints (including the gateway) register with their information, you don't need to manually enter any endpoints in the GK.

Followed by the # ....

Hardcoding GK information makes it very easy for calls to fail because something has been changed on the endpoint of a fat finger during config. I

If you set the unit back to factory defaults "I believe" Plug and Play" all you should need to do is enable the GK, and reconfigure the gateway paramaters. Just make sure you gateway service preifx is listed in the services definition talbe. I don't have a 3520 or 3510 at my disposal so I am doing this from memory... Sorry.......

New Member

Re: IP/VC 3520 configuration help!

Thanks

What could go wrong with TCS4 inward routing???

"Hardcoding GK information makes it very easy for calls to fail because something has been changed on the endpoint of a fat finger during config"

Im not sure i understand the above

regards

New Member

Re: IP/VC 3520 configuration help!

Hi,

Assuming you imply typo errors while hardcoding ..when i implemented automatic i ran into some problems

Given that i start of with only 2 endpoints and there are no hardcode errors what would have been wrong

Enclosed mt log files

VxWorks login: admin

< SD: [0:I_NSY2 CONT] [298037] >n

Password:

< SD: [1:I_NSYN CONT] [298834] >

< SD: ISDN_END [298835] >

< SD: isdn call clearing cause=41 [298835] >

< SD: 1-ISDN clearing cause|class: (41)Temporary failure|Resource unavailable

[298835] >

< SCN: scsesWpEvSendDiscon................ [298835] >

< SCN: scsesWpEvSendDiscon: Port:0 Send:[SCSM_WP_PORT_DISCON_ALL] [298835] >

< SCN: ],EVENT=[SCSM_WP_PORT_DISCON_ALL]> [298835

] >

< APP: <<] , EVENT=[APP_SCN_CALL_DISCONNECT]

>>> [298835] >

< APP: DISCONNECT CALL[0] from WAN cause=41[Temporary failure] [298835] >

< GK: 0000:49:22 _______________________________________________________block 7

6 [298838] >

< GK: 0000:49:22 disengage request from 192.168.20.59:61166 - destination of ca

ll 0. endpoint=3 [298838] >

< GK: 0000:49:22 DCF for call 0 [298838] >

< APP: <<]>>> [298838] >

< APP: <<] , EVENT=[APP_CM_CALL_DISCONNECT]>>> [298839]

>

< APP: <<]>>> [298839] >

< APP: <<] , EVENT=[APP_CM_CALL_IDLE]>>> [298839] >

< GK: 0000:49:22 Hunting for available line after disconnecting. Call 0 [298841

] >

< GK: 0000:49:22 call cannot be completed because destination is busy [298841]

>

< GK: 0000:49:22 (or rejected the call for other reason). Call 0 [298841] >

< GK: 0000:49:22 disconnecting call 0 [298841] >

< APP: ********************************** Calls Status *************************

*************** [298841] >

< APP: call[0] <0:0:30> call[1] <0:0:0> call[2] <0:0:0> call[3] <0:

0:0> [298841] >

< APP: call[4] <0:0:0> call[5] <0:0:0> call[6] <0:0:0> call[7] <0:0

:0> [298841] >

< APP: *************************************************************************

*************** [298841] >

< APP: appCloseAllChannels: callIndx=0 [298841] >

< APP: <<]>>> [298841] >

< SCN: ],EVENT=[SCSM_APP_CLOSE]> [298841] >

< SCN: ------------- Call[1] CLEANUP procedure ------------- [298841] >

< SD: [1:I_ENDO IDL] [298843] >

< GK: 0000:49:22 _______________________________________________________block 7

7 [298844] >

< GK: 0000:49:22 disengage request from 192.168.20.41:1028 - origin of call 0.

endpoint=0 [298844] >

< GK: 0000:49:22 DCF for call 0 [298844] >

< GK: 0000:49:22 clearing call 0 [298845] >

->

< SD: [0:I_NSYN CONT] [300140] >

New Member

Re: IP/VC 3520 configuration help!

We are running the latest version of Via Video & have noticed that it always picks a different port each time it registers with the gatekeeper (3520). Therefore we do not hardcode the terminals in teh gatekeeper.

Some other devices we use are consistent in the ports they use, and we have predefined some of them.

295
Views
0
Helpful
6
Replies
CreatePlease login to create content