Expressway Zone Rule

[yogeshmungekar@gmail.com]

What will be the zone configuration i need to do on VCS-C when all the end point are registered on the itself  VCS-C 

I need to enable SIP URI call to SIP URI call to all endpoint rather than IP to IP.

Because IP to IP call dosen't come over VCS-C, 

As i know zones configuration are towards VCS-E(External call) or towards internal CMS Server for (Bridge Call)

[Anurag Srivastava1]

Hello,

If you register your endpoint on VCS-C by default it will be register in local zone

And you do not need to configure it.

Suppose you have added sip domain abc.com for endpoint registration and you wanted to route the calls  to endpoint you need to make a search rule in which target zone will be local zone.

Further local zones are divided into sub zones.

You can read more about it in admin guides (About the Local Zone and Subzones and registration Control )

https://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/admin_guide/Cisco-VCS-Administrator-Guide-X8-11-4.pdf

Thanks

Please rate if it is helpful...

[yogeshmungekar@gmail.com]

Thanks Anurag for your reply.

But still my internal SIP Uri call not working.

Search (472)
State: Completed
Found: False
Reason: Not Found
Info: Policy Response
Type: SIP (INVITE)
SIPVariant: Standards-based
CallSerial Number: 837945db-9ab8-451b-b67b-e9e8e4b4259b
Tag: 8ba157c1-aa4c-482a-88f6-e0d9568f3e9f
Source (1)
Authenticated: True
Aliases (1)
Alias (1)
Type: Url
Origin: Unknown
Value: 19607@10.1.36.22
Zone (1)
Name: SIP Devices
Type: Local
Path (1)
Hop (1)
Address: 10.225.122.140:43502
Destination (1)
Alias (1)
Type: Url
Origin: Unknown
Value: sip:19613@10.1.36.22
StartTime: 2019-06-27 11:38:28
Duration: 0.01
SubSearch (1)
Type: Transforms
Action: Transformed
ResultAlias (1)
Type: H323Id
Origin: Unknown
Value: 19613@idfcbank.com
SubSearch (1)
Type: Admin Policy
Action: Proxy
ResultAlias (1)
Type: H323Id
Origin: Unknown
Value: 19613@idfcbank.com
SubSearch (1)
Type: FindMe
Action: Proxy
ResultAlias (1)
Type: H323Id
Origin: Unknown
Value: 19613@idfcbank.com
SubSearch (1)
Type: Search Rules
SearchRule (1)
Name: Inbound URI Calls to VC
Zone (1)
Name: LocalZone
Type: Local
Protocol: SIP
Found: False
Reason: Request Timeout
StartTime: 2019-06-27 11:38:28
Duration: 0.01
Gatekeeper (1)
Address: 10.1.36.22:0
Alias (1)
Type: H323Id
Origin: Unknown
Value: 19613@10.1.36.22
Zone (2)
Name: LocalZone
Type: Local
Protocol: H323
Found: False
Reason: Not Found
StartTime: 2019-06-27 11:38:28
Duration: 0
Gatekeeper (1)
Address: 10.1.36.22:0
Alias (1)
Type: H323Id
Origin: Unknown
Value: 19613@10.1.36.22

why it is taking every time H323 protocol.

when i use check pattern option

there the call is routed to actual SIP URI.

Search (15)
State: Completed
Found: True
Type: SIP (OPTIONS)
SIPVariant: Standards-based
CallRouted: True
CallSerial Number: e4ddc4d4-4420-42e2-a798-394c435512aa
Tag: 7efe469f-2018-4442-b2dc-bd4408bb5874
Source (1)
Authenticated: True
Aliases (1)
Alias (1)
Type: Url
Origin: Unknown
Value: 19550@10.1.36.22
Zone (1)
Name: SIP Devices
Type: Local
Path (1)
Hop (1)
Address: 127.0.0.1
Destination (1)
Alias (1)
Type: Url
Origin: Unknown
Value: sip:19500@idfcbank.com
StartTime: 2019-06-27 12:26:03
Duration: 0.01
SubSearch (1)
Type: Transforms
Action: Not Transformed
ResultAlias (1)
Type: Url
Origin: Unknown
Value: 19500@idfcbank.com
SubSearch (1)
Type: Admin Policy
Action: Proxy
ResultAlias (1)
Type: Url
Origin: Unknown
Value: 19500@idfcbank.com
SubSearch (1)
Type: FindMe
Action: Proxy
ResultAlias (1)
Type: Url
Origin: Unknown
Value: 19500@idfcbank.com
SubSearch (1)
Type: Search Rules
SearchRule (1)
Name: Inbound URI Calls to VC
Zone (1)
Name: LocalZone
Type: Local
Protocol: SIP
Found: True
StartTime: 2019-06-27 12:26:03
Duration: 0
Gatekeeper (1)
Address: 10.1.36.22:0
Alias (1)
Type: Url
Origin: Unknown
Value: 19500@10.1.36.22

[Anurag Srivastava1]

Hello,

You need to check with what URI your endpoints are registered and then accordingly you need to make search rule and select protocol to sip only.
I can see that your call arrives to expressway with "" 19613@10.1.36.22" and then getting transformed to "19613@idfcbank.com"

And it is taking H323 search only because through SIP it was not able to find any successful match. 
If you are only using SIP for registration the you should make a search rule like below-

First try to make specific and if all works then play with any pattern..

Thanks

Please rate if it is helpful and mark as accepted solution if applicable..

[yogeshmungekar@gmail.com]

Hi Anurag,

As the given solution, i tried but it didn't worked.

Does it required a valid certificate on EXP-C, because it is currently expired,  to work SIP uri calling 

[Anurag Srivastava1]

Hello,

That's what i mentioned in my previous update you need to check what is the URI of your devices?

You are changing number@domain again to number@ip?

Are your device URI having number@ip?

Also what uri the far end is dialing?

Do one thing register one endpoint with number@domain and make the exact search rule that i mentioned?

And also dial same number@domain and check if it works.

And if it works then make it generic.

Thanks.

Please rate if it is helpful..

[yogeshmungekar@gmail.com]

End point has Sip URI as "alias@ip address(exp-c)"

1) i had checked simple making search rule from local zone to local zone. but it didn't worked.

2) i have make transforms from ip to domain and search rule as domain to IP address(exp-c), still it didn't worked.

i tried both ways in check pattern option and perform a test rule. both works well.

but in actual search rule it is not working.

in search history it show Request-timeout and searching.

• Search (195)
• • State: Completed
• • Found: False
• • Reason: Not Found
• • Info: Policy Response
• • Type: SIP (INVITE)
• • SIPVariant: Standards-based
• • CallSerial Number: 3ca0973f-2068-497f-baef-aab9e560c234
• • Tag: f2888993-207d-41c9-88ad-7d2deb00d56b
• • Source (1)
  • • Authenticated: True
  • • Aliases (1)
    • • Alias (1)
      • • Type: Url
      • • Origin: Unknown
      • • Value: 19607@10.1.36.22
  • • Zone (1)
    • • Name: SIP Devices
    • • Type: Local
  • • Path (1)
    • • Hop (1)
      • • Address: 10.225.122.140:54347
• • Destination (1)
  • • Alias (1)
    • • Type: Url
    • • Origin: Unknown
    • • Value: sip:19613@10.1.36.22
• • StartTime: 2019-06-28 10:37:38
• • Duration: 0.02
• • SubSearch (1)
  • • Type: Transforms
  • • Action: Transformed
  • • ResultAlias (1)
    • • Type: H323Id
    • • Origin: Unknown
    • • Value: 19613@idfcbank.com
  • • SubSearch (1)
    • • Type: Admin Policy
    • • Action: Proxy
    • • ResultAlias (1)
      • • Type: H323Id
      • • Origin: Unknown
      • • Value: 19613@idfcbank.com
    • • SubSearch (1)
      • • Type: FindMe
      • • Action: Proxy
      • • ResultAlias (1)
        • • Type: H323Id
        • • Origin: Unknown
        • • Value: 19613@idfcbank.com
      • • SubSearch (1)
        • • Type: Search Rules
        • • SearchRule (1)
          • • Name: Inbound URI Calls to VC
          • • Zone (1)
            • • Name: LocalZone
            • • Type: Local
            • • Protocol: SIP
            • • Found: False
            • • Reason: Request Timeout
            • • StartTime: 2019-06-28 10:37:38
            • • Duration: 0.01
            • • Gatekeeper (1)
              • • Address: 10.1.36.22:0
              • • Alias (1)
                • • Type: H323Id
                • • Origin: Unknown
                • • Value: 19613@10.1.36.22
          • • Zone (2)
            • • Name: LocalZone
            • • Type: Local
            • • Protocol: H323
            • • Found: False
            • • Reason: Not Found
            • • StartTime: 2019-06-28 10:37:38
            • • Duration: 0
            • • Gatekeeper (1)
              • • Address: 10.1.36.22:0
              • • Alias (1)
                • • Type: H323Id
                • • Origin: Unknown
                • • Value: 19613@10.1.36.22

[Anurag Srivastava1 · Accepted solution]

Hello

When you have registered your endpoint with " alias@ip address(exp-c)" then why you are transforming to domain 

disable transform and make a simple search rule with exact pattern and target it to local zone.

Can you go under registered devices and check how your endpoint is registered there and then you need to make a search rule.

Thanks.

[yogeshmungekar@gmail.com]

Tried just now, as you said

Search (215)
State: Completed
Found: False
Reason: Request Timeout
Info: Request Timeout
Type: SIP (INVITE)
SIPVariant: Standards-based
CallSerial Number: 73a21aab-61a2-40bc-bbae-fcc53d80f4f2
Tag: b98353f3-5a8a-4234-94d5-a88b1c7b204b
Source (1)
Authenticated: True
Aliases (1)
Alias (1)
Type: Url
Origin: Unknown
Value: 19607@10.1.36.22
Zone (1)
Name: SIP Devices
Type: Local
Path (1)
Hop (1)
Address: 10.225.122.140:54347
Destination (1)
Alias (1)
Type: Url
Origin: Unknown
Value: sip:19613@10.1.36.22
StartTime: 2019-06-28 12:09:38
Duration: 0.04
SubSearch (1)
Type: Transforms
Action: Not Transformed
ResultAlias (1)
Type: Url
Origin: Unknown
Value: 19613@10.1.36.22
SubSearch (1)
Type: Admin Policy
Action: Proxy
ResultAlias (1)
Type: Url
Origin: Unknown
Value: 19613@10.1.36.22
SubSearch (1)
Type: FindMe
Action: Proxy
ResultAlias (1)
Type: Url
Origin: Unknown
Value: 19613@10.1.36.22
SubSearch (1)
Type: Search Rules
CallsToUnknownIPAddresses (2)
Mode: Direct
Zone (1)
Name: DefaultZone
Type: Default
Protocol: SIP
Found: False
Reason: Request Timeout
StartTime: 2019-06-28 12:09:38
Duration: 0.01
Gatekeeper (1)
Alias (1)
Type: Url
Origin: Unknown
Value: 19613@10.1.36.22
Zone (2)
Name: DefaultZone
Type: Default
Protocol: H323
Found: False
Reason: Temporary failure - Gatekeeper resources - Out of call resources
StartTime: 2019-06-28 12:09:38
Duration: 0.02
Gatekeeper (1)
Address: 10.1.36.22:1720
Alias (1)
Type: Url
Origin: Unknown
Value: 19613@10.1.36.22

[PJMack]

Based on the thread above - I am guessing you don't have your endpoints registered with full SIP URI's. Can you tell us what URI's you have the endpoints in question registered with?

If you have two endpoints and one is registered as "1234" (no @domain) and your other is "5678" you will have a problem, because if you SIP dial 5678 from the first one, the endpoint wants (needs) to dial a full URI - since it has no domain, it's going to append @ip of the VCS it's registered to. The reverse would be true also, and these calls would never connect since the SIP URI won't actually exist. 

You need a full URI - so create a SIP domain on the VCS of "abc" (whatever is appropriate for you), and then change the endpoint registration to match, so now they will be 1234@abc.com and 5678@abc.com. Now if I'm at the first one I can dial 5678 and it will work - when you don't dial the full URI the endpoint will automatically append the same domain you are using, so it will become 5678@abc.com, find the matching registration and the call will connect. 

hope this helps