Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1876
Views
0
Helpful
14
Replies

External Codecs Through the VCS

Brandon Rebbe
Level 1
Level 1

‎08-20-2012 05:26 PM - edited ‎03-17-2019 11:38 PM

This may be a basic question and i apologize. I have not been to my level two class and my client is implementing already.

I have a Movi Expressway Starter Pack w/firewall option and four C40 Codecs

Everything is working, all the clients can talk, everything is registered h.323 and SIP.

Question:  My client (site A) has a client (site B) that wants to be able to call thier codec.  Site B is not registered to our VCS so how do they call our specific Codec behind the VCS.

I thought it would be somthing like codec@fqdn. So if the h323 or SIP alias was room224@test.com Side B would use that.

But i am not sure how that would be routed with DNS?  The Movi client al use the find me addresses like room224@test.com and those work great but the Movi clients are on the VCS.

SOOO

How do i make sure that whatever address it should be is going to be routed to the

The client has setup an a record of movi.test.com which is routed to the IP of the VCS expressway

Labels:
0 Helpful
14 Replies 14

Patrick Sparkman
VIP Alumni
VIP Alumni

‎08-20-2012 05:42 PM

You would need to implement DNS SVR records to route H323 and SIP calls to your VCS, an A record simply isn't enough.  We had the same issue recently, until we implemented our SVR records.

The following records that we implemented were provided to use from one of our Cisco reps:

  • _h323cs._tcp.. IN SRV 10 10 1720
  • _sips._tcp.. IN SRV 10 10 5061
  • _sip._tcp.. IN SRV 10 10 5060
  • _h323ls._udp.. IN SRV 10 10 1719
  • _sip._udp.. IN SRV 10 10 5060
  • _sips._tls.. IN SRV 10 10 5061
  • _sip._tls.. IN SRV 10 10 5061

SIP Domain needs to be routable FQDN, such as your company's domain or movi.test.com as in your previous message.

For example the first record (_h323cs._tcp..) indicates the service (h323) the

protocol (tcp) the priority (10) and weight (10) and the port (1720) to use when connecting to the

server (FQDN address of Expressway).

There are also some documents that cover this in detail that you might want to check out here in the forums.

0 Helpful

Tomonori Taniguchi
Cisco Employee
Cisco Employee

‎08-20-2012 05:49 PM

If client-B support URI dialing (and have proper DNS configuration) and able to reach VCS-E (for both call signal and media routing), client-B able to make a call to Endpoint/UA on VCS-E Starter Pack (assume your Endpoint/UA registered on VCS-E SP with URI format and also have local search rule with matching it).

Addition to above, your VCS-E SP need DNS registration (either SRV or A-record but highly recommend for SRV).

For these configuration, call initiator able to reach out VCS-E SP even dialing with URI format.

For more information about DNS SRV, please refer to https://supportforums.cisco.com/docs/DOC-25395 and VCS administrator guide.

One additional tip that VCS-E SP has limitation for interworking call (please check detail in VCS administrator guide).

0 Helpful

Tomonori Taniguchi
Cisco Employee
Cisco Employee
In response to Tomonori Taniguchi

‎08-20-2012 05:52 PM

Additional reference, https://supportforums.cisco.com/message/3676656#3676656, in this support community as your reference.

0 Helpful

Patrick Sparkman
VIP Alumni
VIP Alumni
In response to Tomonori Taniguchi

‎08-20-2012 05:56 PM

Without SVR records you could connect to an internal codec via the following method, which is what we did until we finally got our SVR records in place.

codec@

0 Helpful

Brandon Rebbe
Level 1
Level 1

‎08-20-2012 05:57 PM

Forgot to mention that we already setup all the SRV records as well.  i learned my lesson on that when i setup my first movi box.  

I think what i am missing are some search rules in the VCS.  I will check ou the Docs you sugested and let you know.

Thanks for the help!!!

0 Helpful

Tomonori Taniguchi
Cisco Employee
Cisco Employee
In response to Brandon Rebbe

‎08-20-2012 06:00 PM

As mention earlier, if all your Endpoint/UA register with URI format (not E.164 alias), then any match pointing to local zone should works for simple call search.

You may use locate tool on VCS Web GUI for testing the search rule.

Also https://supportforums.cisco.com/docs/DOC-25084 for your reference if need for regex base search rule configuration addition to administrator guide.

0 Helpful

Brandon Rebbe
Level 1
Level 1

‎08-20-2012 06:39 PM

It looks like my client did not setup thier SRV records like i asked them too!!!!!  I just did several ns lookup tests and nothing shows up.  So i think i may have found the answer to my question. 

Thank You

0 Helpful

Brandon Rebbe
Level 1
Level 1

‎08-23-2012 11:16 AM

Same issue but reverse...  I am trying to dial an IP address from a c40 that is registered tot he VCS movi starte pack.  This has the dual nic option too.

I have put in my DNS zone, Search rules for any IP address and still cannot connect.  I know the other codec works becuase i can ping it from the vcs and i can get into it from the same network. 

the log gives me this:

Aug 23 13:09:40tvcs: Event="Call Rejected" Service="H323" Src-ip="172.17.43.7" Src-port="11025" Src-alias-type="H323" Src-alias="room334@normal.org" Src-alias-type="E164" Src-alias="334" Dst-ip="173.15.99.213" Call-serial-number="b3d6f1b0-ed4d-11e1-ae55-0010f32381a2" Tag="b3d6f2dc-ed4d-11e1-b986-0010f32381a2" Protocol="TCP" Response-code="Destination not found" Level="1" UTCTime="2012-08-23 18:09:40,551"
Aug 23 13:09:40tvcs: Event="Search Completed" Service="H323" Src-alias-type="H323" Src-alias="room334@normal.org" Src-alias-type="E164" Src-alias="334" Dst-ip="173.15.99.213" Call-serial-number="b3d6f1b0-ed4d-11e1-ae55-0010f32381a2" Tag="b3d6f2dc-ed4d-11e1-b986-0010f32381a2" Detail="found:FALSE, searchtype:Setup" Level="1" UTCTime="2012-08-23 18:09:40,550"

it says destination not found but i can ping the ip address.  Does this mean my search rule is not working?

0 Helpful

Patrick Sparkman
VIP Alumni
VIP Alumni
In response to Brandon Rebbe

‎08-23-2012 05:59 PM

Brandon - Try doing a locate search to see where the search is failing, it will help you determine if it's your search rules or something else.

Maintenance > Tools > Locate

0 Helpful

Tomonori Taniguchi
Cisco Employee
Cisco Employee
In response to Brandon Rebbe

‎08-23-2012 06:00 PM

What is configuration for “Calls to unknown IP addresses” under Dial plan configuration, “Direct”?

0 Helpful

Brandon Rebbe
Level 1
Level 1
In response to Tomonori Taniguchi

‎08-24-2012 06:17 PM

I am on direct dial

This is what i get with SIP when i do a locate

  • Search (4)
  • State: Completed
  • Found: False
  • Reason: Request Timeout
  • Type: SIP (OPTIONS)
  • CallSerial Number: 6a884210-ee52-11e1-a52e-0010f32381a2
  • Tag: 6a8842f6-ee52-11e1-873d-0010f32381a2
  • StartTime: 2012-08-24 20:15:53
  • Duration: 0.01
  • Source (1)
    • Authenticated: False
    • Aliases (1)
      • Alias (1)
        • Type: Url
        • Origin: Unknown
        • Value: xcom-locate
    • Zone (1)
      • Name: DefaultZone
      • Type: Default
    • Path (1)
      • Hop (1)
        • Address: 127.0.0.1
  • Destination (1)
    • Alias (1)
      • Type: Url
      • Origin: Unknown
      • Value: sip:173.15.99.213
    • SubSearch (1)
      • Type: Transforms
      • Action: Not Transformed
      • ResultAlias (1)
        • Type: Url
        • Origin: Unknown
        • Value: 173.15.99.213
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: Url
          • Origin: Unknown
          • Value: 173.15.99.213
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: Url
            • Origin: Unknown
            • Value: 173.15.99.213
          • SubSearch (1)
            • Type: Search Rules
            • CallsToUnknownIPAddresses (1)
              • Mode: Direct
              • Found: True
              • Zone (1)
                • Name: DefaultZone
                • Type: Default
                • Protocol: SIP
                • Found: False
                • Reason: Request Timeout
                • Gatekeeper (1)
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 173.15.99.213

    This is what i get with H323

    • Search (6)
    • State: Completed
    • Found: True
    • Type: H323 (LRQ)
    • CallRouted: True
    • CallSerial Number: a71be79a-ee52-11e1-8242-0010f32381a2
    • Tag: a71be88a-ee52-11e1-adaa-0010f32381a2
    • StartTime: 2012-08-24 20:17:35
    • Duration: 0.01
    • Source (1)
      • Authenticated: False
      • Aliases (1)
        • Alias (1)
          • Type: H323Id
          • Origin: Unknown
          • Value: xcom-locate
      • Zone (1)
        • Name: DefaultZone
        • Type: Default
    • Destination (1)
      • Alias (1)
        • Type: H323Id
        • Origin: Unknown
        • Value: 173.15.99.213
    • SubSearch (1)
      • Type: Transforms
      • Action: Not Transformed
      • ResultAlias (1)
        • Type: H323Id
        • Origin: Unknown
        • Value: 173.15.99.213
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: H323Id
          • Origin: Unknown
          • Value: 173.15.99.213
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: H323Id
            • Origin: Unknown
            • Value: 173.15.99.213
          • SubSearch (1)
            • Type: Search Rules
            • CallsToUnknownIPAddresses (1)
              • Mode: Direct
              • Found: True
              • Zone (1)
                • Name: DefaultZone
                • Type: Default
                • Protocol: H323
                • Found: True
                • Gatekeeper (1)
                  • Address: 173.15.99.213:1720
                  • Alias (1)
                    • Type: H323Id
                    • Origin: Unknown
                    • Value: 173.15.99.213

      0 Helpful

      Brandon Rebbe
      Level 1
      Level 1
      In response to Brandon Rebbe

      ‎08-24-2012 07:22 PM

      The IP address i was dialing was behind a VCS.  I called the URI of the IP and it works great.  I found some test IP addresses and everything worked.  My client neglected to tell me the other side was behind a VCS.  So i guess i am my own issue. 

      0 Helpful

      Tomonori Taniguchi
      Cisco Employee
      Cisco Employee
      In response to Brandon Rebbe

      ‎08-24-2012 07:33 PM

      You may also test calling IP address of VCS after configure that SIP UAs URL as “Fallback alias” under Dial plan configuration.

      When VCS receive the call directly own IP address, VCS will proceed the call to alias that configured as “Fallback alias”.

      If customer has support desk, often this feature works well by forwarding the call to support desk URI.

      0 Helpful

      Brandon Rebbe
      Level 1
      Level 1
      In response to Tomonori Taniguchi

      ‎08-24-2012 07:36 PM

      THanks for the tip i will set that up with the IT desk.  I have the system integrated with thier call manager so i will send it to them. 

      THanks!!!

      0 Helpful
      Customers Also Viewed These Support Documents