Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Unable to complete call to free cisco jabber client

When calling from either my Edge 95 or Jabber (Movi) client to a user using the free jabber video client the call does not go through. They can call us. I checked the search details on the call i find:

  • SearchRule (3)
    • Name: DNS
    • Zone (1)
      • Name: DNS
      • Type: DNS
      • Protocol: SIP
      • Found: False
      • Reason: Server Internal Error
      • StartTime: 2014-09-09 15:34:37
      • Duration: 3.16
      • Gatekeeper (1)
        • Alias (1)
          • Type: Url
          • Origin: Unknown
          • Value: xxxxxxx@jabber.com

 

When calling a client not using the free Jabber video service the call works fine:

 

  • SearchRule (3)
    • Name: DNS
    • Zone (1)
      • Name: DNS
      • Type: DNS
      • Protocol: SIP
      • Found: True
      • StartTime: 2014-09-09 15:29:39
      • Duration: 2.42
      • Gatekeeper (1)
        • Alias (1)
          • Type: Url
          • Origin: Unknown
          • Value: FFFF.LLLLL@xxx.com

 

Any idea why the free client is failing?

6 REPLIES
Cisco Employee

Hi vonhasch,Your outbound

Hi vonhasch,

Your outbound call to a Cisco Jabber Video beta user is restricted because it is not secure.  This service requires you to follow security standards in order reach a user from your network.  Approved CA certs can be found here:

https://supportforums.cisco.com/document/97931/trusted-public-root-cas-b2b-telepresence

These certs are the same for CJV Beta as they are for Cisco Webex Telepresence.  

Regards,
Jason

New Member

Is this something new? I've

Is this something new? I've been making calls to Cisco Jabber Video for quite some time now and I haven't made any changes to my certificates. Also I can make calls to other Cisco Jabber Video users.

Cisco Employee

Hi Vonhasch,This is not new.

Hi Vonhasch,

This is not new.  This is how the service has always worked.  This service does not allow self-signed certs.  Based on what you are saying above, is this issue happening only when you call @jabber.com users?  

Also, by saying you've been making calls to Cisco Jabber Video, are the users using this domain, @jabber.com or a different domain?  

You can make calls to other Cisco Jabber Video users?  Are they using the @jabber.com domain?

What scope of your calls are not working to @jabber.com users; one, a few, all?

Please provide more detail and maybe some logs from your gatekeeper that help identify the issue.

Regards,
Jason

New Member

Jason, The calls I'm making

Jason,

 

The calls I'm making are to @jabber.com. 95% of the time it works. This call was one of the few that didn't. I would think that if my problem was due to certs it would either work or it wouldn't. Typically if we cannot connect to a @jabber.com user they can call us. Here is a call I made this morning, worked fine;

 

  • Search (349)
    • State: Completed
    • Found: True
    • Type: SIP (INVITE)
    • CallRouted: True
    • CallSerial Number: 2ac0d45b-6f48-4a7b-9081-354913f5e0cb
    • Tag: 53d3f087-a22c-459a-84ab-ea29aa996878
    • Source (1)
      • Authenticated: True
      • Aliases (1)
        • Alias (1)
          • Type: Url
          • Origin: Unknown
          • Value: Carl.VonHassel@jud.ct.gov
      • Zone (1)
        • Name: TraversalServ
        • Type: TraversalServer
      • Path (1)
        • Hop (1)
          • Address: 10.16.7.77:5061
        • Hop (2)
          • Address: 10.16.11.85:56427
    • Destination (1)
      • Alias (1)
        • Type: Url
        • Origin: Unknown
        • Value: sip:*******@jabber.com
    • StartTime: 2014-09-19 11:04:49
    • Duration: 10.47
    • SubSearch (1)
      • Type: Transforms
      • Action: Not Transformed
      • ResultAlias (1)
        • Type: Url
        • Origin: Unknown
        • Value: *******@jabber.com
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: Url
          • Origin: Unknown
          • Value: ******@jabber.com
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: Url
            • Origin: Unknown
            • Value: ******@jabber.com
          • SubSearch (1)
            • Type: Search Rules
            • SearchRule (1)
              • Name: Local
              • Zone (1)
                • Name: LocalZone
                • Type: Local
                • Protocol: SIP
                • Found: False
                • Reason: Not Found
                • StartTime: 2014-09-19 11:04:49
                • Duration: 0
                • Gatekeeper (1)
                  • Address: 198.177.9.20:0
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: ********@jabber.com
              • Zone (2)
                • Name: LocalZone
                • Type: Local
                • Protocol: H323
                • Found: False
                • Reason: Not Found
                • StartTime: 2014-09-19 11:04:49
                • Duration: 0
                • Gatekeeper (1)
                  • Address: 198.177.9.20:0
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: *********@jabber.com
            • SearchRule (3)
              • Name: DNS
              • Zone (1)
                • Name: DNS
                • Type: DNS
                • Protocol: SIP
                • Found: True
                • StartTime: 2014-09-19 11:04:49
                • Duration: 10.46
                • Gatekeeper (1)
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: *******@jabber.com
Cisco Employee

Hi Vonhasch,Intermittent

Hi Vonhasch,

Intermittent issues are tough to troubleshoot without the proper debug logging provided.  It calls work to the same caller, and then don't work for whatever reason, but then that caller can still call you; it sounds like it could be a network issue of some sort.  However, is this what you are seeing?  You only specified you can make successful calls 95% of the time.  

Are calls failing to the same caller, or is it intermittent?

What we need are debug logs from your gatekeeper at the time of the failure.  Also, does the @jabber user receive the call and it just doesn't connect?  or the call never reaches the user?

If the @jabber user can see the call coming in, then we need sip debug logs from the client too.  I have added some instructions on how to do this from the client side.

Pings and trace routes will also be good from your network out to these IP addresses: 199.19.190.26, 199.19.190.28, and 199.19.190.22

Thanks,
Jason

New Member

Jason, When the call fails it

Jason,

 

When the call fails it is not usually to the same user. Sometimes it is if we repeatedly call them but we usually have them call us if we can't call them. Next time it happens I'll obtain all the logs and post them. Almost always when the call doesn't work to them it never reaches them (they get no incoming call). I'll also send the traceroutes. However even though the free Jabber Video Client has been of great use to us we'll have Jabber Guest available soon and will use it predominantly. 

255
Views
0
Helpful
6
Replies