VCS 7.2.2
Dialing a SIP URI from a SIP Endpoint, the VCS does the appropriate search.
It looks for the URI and does a SIP lookup first (which it does not find although it is registered)
Then it times out, and finds it via H.323.
The Endpoint that is being dialed is dual registered with the same name.
1. I checked the registrations, and it looks fine. This particular EP is registered to a VCS Express.
2. I checked the SIP search and it matches the SIP registration (but does not find it).
3. VCS has both TCP and UDP enabled. Is this the reason that it might not find the SIP endpoint?
Below is part of the search. And below that is the SIP registration.
Search (131)
State: Completed
Found: True
Type: SIP (INVITE)
CallRouted: True
CallSerial Number: d517c746-df4b-11e2-9854-0010f31ed420
...
Destination (1)
Alias (1)
Type: Url
Origin: Unknown
Value: sip:fed.adm.101@acme.com
StartTime: 2013-06-27 10:05:56
Duration: 36.8
SearchRule (2)
Name: Local zone Any Rule
Zone (1)
Name: LocalZone
Type: Local
Protocol: SIP
Found: False
Reason: Request Timeout
StartTime: 2013-06-27 10:05:56
Duration: 32.01
Gatekeeper (1)
Address: 1xx.1xx.1xx.xx:0
Alias (1)
Type: H323Id
Origin: Unknown
Value: fed.adm.101@acme.com
Zone (2)
Name: LocalZone
Type: Local
Protocol: H323
Found: True
StartTime: 2013-06-27 10:06:28
Duration: 4.5
Gatekeeper (1)
Address: 1xx.1xx.1xx.xx:0
Alias (1)
Type: H323Id
Origin: Unknown
Value: fed.adm.101@acme.com
SIP Reg
Status
Active true
Name fed.adm.101@acme.com
Protocol SIP
Type SIP UA
Authenticated True
Node DefaultSubZone
Vendor information TANDBERG/68 (L6.1)
Serial number 85615b54-dec9-11e2-91bb-0010f31ed420
Creation time 2013-06-26 18:33:08
Duration 15 hours 37 minutes 6 seconds
AOR fed.adm.101@acme.com
Contact sip:fed.adm.101@198.72.197.193:5060
