Profile with VCS StarterPack

[Paulo Ferreira]

Hello,

I have a VCS Starter Pack with jabber video clients and one Profile with C40.

I'm trying to attend the external calls directly in the profile, but without sucess.

In VCS I can see that the Codec is registered, although going to the Locate Tool in VCS appears:

"

• Search (10)
  

• State: Completed
  

• Found: False
  

• Reason: Not Found
  

• Type: H323 (LRQ)
  

• CallSerial Number: 159f54de-3586-11e2-8d85-0010f323030a
  

• Tag: 159f5614-3586-11e2-ae4b-0010f323030a
  

• Source (1)
  
• • Authenticated: True
    
• • Aliases (1)
    
  • • Alias (1)
      
    • • Type: H323Id
        
    • • Origin: Unknown
        
    • • Value: xcom-locate
        
  • Zone (1)
    
    • Name: DefaultZone
      
  • 
    
    • Type: Default
      

"

Putting one jabber video receiving the external call all works fine and the locate tool found the device.

This is some kind of bug?

The VCS StartePack as the version X7.2.1 and Profile as the version TC5.0.1

Regards

[Tomonori Taniguchi · Accepted solution]

Can you provide following information to understand your situation?

• What is dialed URL from Jabber Video to Profile system?
  
• What alias does Profile system registered on VCS-E Starter Pack?
  
• What search rule have you configured on VCS-E Starter Pack?
  
• Any alias transform configured on VCS-E Starter Pack?
  

[Paulo Ferreira]

Hello Tomonori,

thanks for your questions.

Here are the answer to your questions:

• What is dialed URL from Jabber Video to Profile system? salareuniao@miranda.local
  
• What alias does Profile system registered on VCS-E Starter Pack? salareuniao@miranda.local
  
• What search rule have you configured on VCS-E Starter Pack?
  

1. 1 search rule with Any Alias to Local Zone, priority 50;
   
2. 1 search rule with Any Alias to DNS Zone, priority 60;
   
3. 1 search rule with Any IP Address to DNS Zone, priority 70;
   

• Any alias transform configured on VCS-E Starter Pack? Not for the profile.
  

Regards

Paulo Ferreira

PS: I clicked wrongly in right answer and I cant unselect

[Tomonori Taniguchi]

Configuration looks fine.

BTW, does Profile system registered on VCS-E SP as H323 device with authentication parameters?

If so does “H323 <-> SIP interworking mode” set to “Registered only”?

The “Locate” tool will return “Found: True” for any H323 Endpoint registered on VCS while "Locate" search done with H323 as protocol.

But if incoming call from SIP UA, then search will be failed if interworking call is disabled.

If this parameter properly configured as well, then need a debug level diagnostic log to understand what causing call setup failure between Jabber Video and Profile Endpoint registered on VCS-E SP.

[Paulo Ferreira]

Now the profile is just SIP registered.

The Interworking mode is ON.

But the problem it's not beetween jabber anda profile, it's from outside to profile.

[Tomonori Taniguchi]

Oh ok, I misunderstand your problem.

Default configuration for SIP-H323 interworking for VCS-E Starter Pack is “Registered Only”.

VCS-E Starter Pack provide SIP-H323 interworking between locally registered H.323 and SIP devices but not interworking “gateway” call capability.

Therefore when Profile Endpoint (registered as SIP device on VCS-E SP) failed to establish call when call received from unregistered endpoint (call protocol = h323).

Please try register your Profile Endpoint on VCS-E SP both with SIP (currently registered as salareuniao@miranda.local) and also register as H323 (configure H323 ID as salareuniao@miranda.local and enable authentication mode (xConfiguration H323 Profile 1 Authentication Mode: On) with authentication loginname and password).

You should now able to establish incoming call from unregistered endpoint even call protocol is H.323.