ā06-18-2013 02:01 AM - edited ā03-18-2019 01:18 AM
hi i have an implimentation 1vcsc and 1vcse in dmz.
i configured sip and h323 and both are active in traversal zone.
and i regisered 1 polycom end point to vcsc and 1 polycom end point to vcse.
but am not able to make a call between them. i tried both side.
please sugest me any thing i need to create links? or default link is sufficient to communicate between them.
Thanks
veera
ā06-18-2013 02:15 AM
In short, all components need to properly talk to each other
* network / firewall
* basic config vcs
* config endpoints
* proper registations
* proper dialplan
* proper calls
* ...
There are many points where it can fail.
I would recomend to first check out:
To see that the basics are done.
If that is in place tell us a bit more about the deployment, what you registered the systems with,
what you dialed, how your search registrations show up on the vcss, how the search / call histroty looks like
and so on, ...
Please remember to rate helpful responses and identify
ā06-18-2013 02:33 AM
Hi martin thanks for the quick respose,
i configured both the devices using the same dacument what you suggested in the link.
is it any thing i need to create any links in both the devices because in warning it is showing expected default links missing.
i tried ip and e164 number to dail the end point.
FYI.. if i register both the end points to vcsc or vcse i can make a call between them without any issue.
thanks.
veera.
ā06-18-2013 03:49 AM
Hi Martin.
I think there is a link problem between the devices(vcs) so that am not able to make a call. It is clearly showing in vcs warnings default link is missing.
Please suggest me how to add default link in vcs.
Thanks.
veera.
ā06-18-2013 10:25 AM
Hi Martin,
Below find the call and search details of the call which i initiated from the endpoint which is registred to vcsc.
s.s.s.s is the source ip
d.d.d.d is the destination ip
Displaying 2 searches for this Call Tag.plural
Search (13)
State: Completed
Found: True
Type: H323 (ARQ)
CallRouted: True
CallSerial Number: a67aa35e-d825-11e2-a35d-0010f315936c
Tag: a67aa566-d825-11e2-b763-0010f315936c
StartTime: 2013-06-18 20:14:59
Duration: 0
Source (1)
Authenticated: False
Aliases (1)
Alias (1)
Type: H323Id
Origin: Endpoint
Value: BDC2
Alias (2)
Type: E164
Origin: Endpoint
Value: 800201
Zone (1)
Name: LocalZone
Type: Local
Path (1)
Hop (1)
Address: s.s.s.s
Destination (1)
Alias (1)
Type: IPAddress
Origin: Unknown
Value: d.d.d.d
SubSearch (1)
Type: Transforms
Action: Not Transformed
ResultAlias (1)
Type: IPAddress
Origin: Unknown
Value: d.d.d.d
SubSearch (1)
Type: Admin Policy
Action: Proxy
ResultAlias (1)
Type: IPAddress
Origin: Unknown
Value: d.d.d.d
SubSearch (1)
Type: FindMe
Action: Proxy
ResultAlias (1)
Type: IPAddress
Origin: Unknown
Value: d.d.d.d
SubSearch (1)
Type: Search Rules
CallsToUnknownIPAddresses (1)
Mode: Direct
Found: True
Zone (1)
Name: DefaultZone
Type: Default
Protocol: H323
Found: True
Gatekeeper (1)
Address: d.d.d.d:1720
Alias (1)
Type: IPAddress
Origin: Unknown
Value:d.d.d.d
Search (14)
State: Completed
Found: False
Reason: Destination not found
Type: H323 (Setup)
CallSerial Number: a67aa35e-d825-11e2-a35d-0010f315936c
Tag: a67aa566-d825-11e2-b763-0010f315936c
StartTime: 2013-06-18 20:14:59
Duration: 0.12
Source (1)
Authenticated: False
Aliases (1)
Alias (1)
Type: H323Id
Origin: Unknown
Value: BDC2
Alias (2)
Type: E164
Origin: Unknown
Value: 800201
Zone (1)
Name: LocalZone
Type: Local
Destination (1)
Alias (1)
Type: IPAddress
Origin: Unknown
Value:d.d.d.d
SubSearch (1)
Type: Transforms
Action: Not Transformed
ResultAlias (1)
Type: IPAddress
Origin: Unknown
Value:d.d.d.d
SubSearch (1)
Type: Admin Policy
Action: Proxy
ResultAlias (1)
Type: IPAddress
Origin: Unknown
Value:d.d.d.d
SubSearch (1)
Type: FindMe
Action: Proxy
ResultAlias (1)
Type: IPAddress
Origin: Unknown
Value: d.d.d.d
SubSearch (1)
Type: Search Rules
CallsToUnknownIPAddresses (1)
Mode: Direct
Found: True
Zone (1)
Name: DefaultZone
Type: Default
Protocol: H323
Found: False
Reason: Destination not found
Gatekeeper (1)
Address: d.d.d.d:1720
Alias (1)
Type: IPAddress
Origin: Unknown
Value: d.d.d.d
and
Call details You are here: Status Calls Calls Call details Call information
State Connection Failed
Start time 2013-06-18 20:14:59
Duration 0 seconds
Tag a67aa566-d825-11e2-b763-0010f315936c
Serial number a67aa35e-d825-11e2-a35d-0010f315936c
Bandwidth
Requested 384 kbps
Allocated 384 kbps
Leg 1
Bandwidth node Default Subzone
Source alias 1 BDC2 (H323Id)
Source alias 2 800201 (E164)
Target alias 1 d.d.d.d(IPAddress)
Protocol H323
Address s.s.s.s:3235
Encryption type None
Reason Called party not registered
Cause Subscriber absent
Additional cause Destination not found
Leg 2
Bandwidth node Default Zone
Target alias 1 d.d.d.d (IPAddress)
Protocol H323
Address vcse ip:1720
Encryption type None
Reason Called party not registered
Cause Subscriber absent
Additional cause Destination not found
Session 1
Status Failed
Media routed False
Call routed True
Participant 1 Leg 1
Participant 2 Leg 2
Bandwidth allocated 384 kbps
Bandwidth requested 384 kbps
Route
Thanks.
veera.
ā06-18-2013 03:55 PM
Please check how these endpoints are registred, and what registation options you have.
If I see it right you are trying to call an ip address? thats in general not what you want if you use a
vcs-c/e.
I think in theory e164 dialing should work with the deployment example from the guide, but I would check
out and implement proper uri dialing.
Anyhow, I did not notice a hit for a search rule towards the traversal zone, ...
Do you have a cisco partner who can help you? Sounds like an easy problem to fix if you sit and interact with the
systems and the config. Via the forum it can end up in endless discussions with a lot of time used, ...
Please remember to rate helpful responses and identify
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide