cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
431
Views
0
Helpful
2
Replies
Highlighted

VCS Control search problem

I'm having difficulty expressing the question I have.  I have 5 systems in my network that are setup as H323 only (E164 only), and I have connections coming into them via my VCS Control.  The dialled string is XXXX@10.14.242.8, where XXXX=the E.164 aliases.  I have a transform that strips the domain from this and until today, all calls have been connecting to all 5 sites using the E.164 alias (see 1st example)

  • Search (67)
    • State: Completed
    • Found: True
    • Type: H323 (Setup)
    • CallRouted: True
    • CallSerial Number: 6e4dd3e7-ef26-4307-8b9b-e9a0912ca0be
    • Tag: c5b1b187-80df-4773-8c4d-a9784648ddc4
    • Source (1)
      • Authenticated: True
      • Aliases (1)
        • Alias (1)
          • Type: H323Id
          • Origin: Unknown
          • Value: Hfx-IWK-HC-FE-R1
        • Alias (2)
          • Type: E164
          • Origin: Unknown
          • Value: 9070
      • Zone (1)
        • Name: DefaultZone
        • Type: Default
    • Destination (1)
      • Alias (1)
        • Type: H323Id
        • Origin: Unknown
        • Value: 3431@10.14.242.8
    • StartTime: 2014-11-20 15:43:31
    • Duration: 0.89
    • SubSearch (1)
      • Type: Transforms
      • Action: Transformed
      • ResultAlias (1)
        • Type: E164
        • Origin: Unknown
        • Value: 3431
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: E164
          • Origin: Unknown
          • Value: 3431
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: E164
            • Origin: Unknown
            • Value: 3431
          • SubSearch (1)
            • Type: Search Rules
            • SearchRule (1)
              • Name: LocalZone Match3(1)
              • Zone (1)
                • Name: LocalZone
                • Type: Local
                • Protocol: H323
                • Found: True
                • StartTime: 2014-11-20 15:43:31
                • Duration: 0.88
                • Gatekeeper (1)
                  • Address: 10.14.242.8:0
                  • Alias (1)
                    • Type: E164
                    • Origin: Unknown
                    • Value: 3431

 

But today, when one of these systems was dialled, the call failed because the VCS C was searching for the system using H.323ID, but still using only the 4 digits.  The other 4 systems, using the same dialling method, and same transform, connected fine. See example of failed search:

 

  • Search (89)
    • State: Completed
    • Found: False
    • Reason: Not Found
    • Type: H323 (Setup)
    • CallSerial Number: 9c46d615-e001-42f4-906d-99678f76d150
    • Tag: 9fe8d2bb-e943-4dfe-b0be-42903543d62c
    • Source (1)
      • Authenticated: True
      • Aliases (1)
        • Alias (1)
          • Type: H323Id
          • Origin: Unknown
          • Value: Hfx-IWK-HC-FE-R1
        • Alias (2)
          • Type: E164
          • Origin: Unknown
          • Value: 9070
      • Zone (1)
        • Name: DefaultZone
        • Type: Default
    • Destination (1)
      • Alias (1)
        • Type: H323Id
        • Origin: Unknown
        • Value: 1431@10.14.242.8
    • StartTime: 2014-11-20 16:50:24
    • Duration: 0.32
  •  
    • SubSearch (1)
      • Type: Transforms
      • Action: Transformed
      • ResultAlias (1)
        • Type: H323Id
        • Origin: Unknown
        • Value: 1431
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: H323Id
          • Origin: Unknown
          • Value: 1431
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: H323Id
            • Origin: Unknown
            • Value: 1431
          • SubSearch (1)
            • Type: Search Rules
            • SearchRule (1)
              • Name: LocalZone Match3(1)
              • Zone (1)
                • Name: LocalZone
                • Type: Local
                • Protocol: H323
                • Found: False
                • Reason: Not Found
                • StartTime: 2014-11-20 16:50:24
                • Duration: 0
                • Gatekeeper (1)
                  • Address: 10.14.242.8:0
                  • Alias (1)
                    • Type: H323Id
                    • Origin: Unknown
                    • Value: 1431
              • Zone (2)
                • Name: LocalZone
                • Type: Local
                • Protocol: SIP
                • Found: False
                • Reason: Not Found
                • StartTime: 2014-11-20 16:50:24
                • Duration: 0
                • Gatekeeper (1)
                  • Address: 10.14.242.8:0
                  • Alias (1)
                    • Type: H323Id
                    • Origin: Unknown
                    • Value: 1431
            • SearchRule (2)
              • Name: TraversalZone Match2
              • Zone (1)
                • Name: ToVCSExpress
                • Type: TraversalClient
                • Protocol: H323
                • Found: False
                • Reason: Not registered - Destination not found
                • StartTime: 2014-11-20 16:50:24
                • Duration: 0.31
                • Gatekeeper (1)
                  • Address: 172.16.1.80:6001
                  • Alias (1)
                    • Type: H323Id
                    • Origin: Unknown
                    • Value: 1431
              • Zone (2)
                • Name: ToVCSExpress
                • Type: TraversalClient
                • Protocol: SIP
                • Found: False
                • Reason: Internal Server Error
                • StartTime: 2014-11-20 16:50:24
                • Duration: 0
                • Gatekeeper (1)
                  • Address: 172.16.1.80:7001
                  • Alias (1)
                    • Type: H323Id
                    • Origin: Unknown
                    • Value: 1431
              •  

So where the 2 searches differ is when the address is transformed.  In the call that works, the type is E164, but in the calls that fail, the type is H323ID.  

1. I've verified that the endpoint in question is registered with the E164 alias 1431.

2. I have unregistered the codec, and re-registered it.  

3. I performed a Defaultlinksadd

The only way I could get the calls to work was to get the dialling system to dial a new number (1600@10.14.242.8), and use a transform to change it to 1431.   

  • ubSearch (1)
    • Type: Transforms
    • Action: Transformed
    • ResultAlias (1)
      • Type: H323Id
      • Origin: Unknown
      • Value: 1431

 

This was an emergency patient consult for a very sick child with heart problems.  I do not want this to happen again, so I need to figure out what happened.  Any further suggestions for me?

2 REPLIES 2
Highlighted
Contributor

Hi Darren,

Just out of curiosity, is there any reason why you would want to dial with the appended VCS IP address? Can you dial just use the E.164 with no transforms?

Assuming all the devices are registered to the single VCS and have the correct E.164 number set in their config (not necessity the H.323 ID which can be and probably should be completely different (and to make matters worse the H.323 ID can contain odd characters such as spaces), then the calls placed should just work.Give it a try.

We run a multiple organisational hierarchical setup that does just this. 

Cheers

 

Highlighted
Engager

As Chris said, ip addresses should not matter on e164 dialing if registered.

 

So something really sounds strange here, so you want to review your setup what exactly

goes wrong here. I would also strongly recommend (as you seem to have some sip

capability running (traversal zone)) that you should look into using proper uris.

 

 

Please remember to rate helpful responses and identify

Content for Community-Ad