Cisco jabber for mac over fortigate vpn problem

Hi all,
We have installed the cisco jabber for mac successfully.Jabber client able to register locally successfully.
Calling and other features working properly. Jabber IM also working fine.
But when we try over vpn its shows error."services are missing".All the ports are open on fortigate firewall.

If you have detailed diagnostics from the Jabber Mac client, this would provide some more context to why it's displaying those errors. (Help > Detailed Logging enabled) (Help > Report a problem)
Another thing to check for would be DNS resolution of the configured servers when the Mac is VPN'd in. If Jabber cannot resolve the DNS name, it will not know where to connect to.
If the diagnostics are pointing towards a connectivity problem, but the firewall says it's wide open, then taking a packet capture on the Mac where Jabber is trying to register may illustrate what's going on at the network layer.

Similar Messages

Cisco Jabber for Mac - Directory Lookup and Contact Fields

Hello,
After having issues myself with Cisco Jabber for Mac 9.2 specifically with Active Directory lookups not working, or contact information not populating (and therefore not being able to call users from the contact list as no telephone information exists) I am including a sample jabber-config.xml file that works for me.
Please note: there are many different ways to configure this. What I will be showing is the method that works for me and my deployment, which is pretty standard.
As always and as a disclaimer, once again, this is what has worked for my deployment scenario. Always keep backups of your configuration files, and always be mindful of anything you have configured already, especially in the jabber-config.xml file.
Background
My deployment is based on CUCM 9, with 1 publisher and 2 subscribers. I also have a CUCM IM & Presence 9.0 server. This assumes that you have already configured your deployment and Jabber is functioning already, albeit with the aforementioned issues.
As for Active Directory, my deployment will be based on Windows 2008 R2 Domain Controllers running in native 2008 mode. For this example, we will be searching directly against one of the DCs with a Global Catalogue role. Please be aware that in large deployments you will have to plan accordingly with regards to lookup traffic from Jabber clients to the DCs.
Also, as of Cisco Jabber for Mac 9, the client no longer can search via the CUCM internal directory (which may be made of local end users, Active Directory synced users, or a mix of both) and this must be done via a LDAP mechanism.
Scenario
In this deployment scenario, Cisco Jabber for Windows is working properly - you can search and add people from Active Directory, and contacts in your contact list have all the appropriate fields populated from Active Directory. However, when trying the same with Jabber for Mac, Jabber for iPhone or Jabber for iPad you notice that you cannot perform a directory lookup, and if you add people directly (for example, [email protected]) the user only has the IM field populated. No telephone, email or additional information is displayed.
Solution
Whereas Cisco Jabber for Windows uses the EDI mechanism (native Windows), whereby when running from a computer that is on the domain (or in the event that you are search for contacts in another Active Directory domain where a domain trust exists) , Jabber for Mac / iPhone / iPad uses the BDI mechanism.
In this case, you will need to provision a jabber-config.xml file that you will upload to your TFTP server (or Publisher) that will be "downloaded" by your Jabber for Mac client and also used by the iPhone and iPad client. You can configure many options in the jabber-config.xml file, but for this example we will place just the information that we need to order for these clients to request and display Active Directory information.
Please note that the configuration may vary depending on your deployment, but at the very least we will be:
- Configuring a DC where we will perform the lookup.
- Configure credentials that will be used to perform the lookup. This will be an Active Directory account that has read rights on the Active Directory domain. Please note that these credentials are saved in plain text in the file, so ensure that the account that you will be using is not privileged.
- Configure the server port that we will be using to perform the lookup.
- Configure the Search Base. This is basically where we want the directory lookup to happen. You can either choose for this lookup to start at the "base" of the domain (and therefore the search will iterate through all the user accounts and and OUs below the root base) or define a specific OU where you want to search.
Caution!
- There is a current limitation with Cisco Jabber for Mac whereby you can only have 1 search base configured. Please keep this in mind if, like me, you have multiple OUs (like an OU for each company in your organization) and under these OUs you have sub OUs as a user account container.
- If using the top level search base, unless you specify a filter, you will potentially be able to search for all user accounts in the domain. You will need to configure the <BDIBaseFilter> parameter if you want to fine tune your search ability.
Steps
These are the steps I have followed. Other steps or considerations may vary.
- Log in to your TFTP server and download the jabber-config.xml file and keep it as a backup. If you are already using the jabber-config.xml file for other purposes, do not worry - you can add your BDI information parameters inside.
- Remove the jabber-config.xml file
- Edit the jabber-config.xml file and configure thus:
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
    <Directory>
        <DirectoryServerType>BDI</DirectoryServerType>
        <BDILDAPServerType>AD</BDILDAPServerType>
        <BDIPrimaryServerName>DOMAIN CONTROLLER IP ADDRESS</BDIPrimaryServerName>
        <BDIPresenceDomain>YOUR PRESENCE DOMAIN</BDIPresenceDomain>
        <BDIServerPort1>3268</BDIServerPort1>
        <BDISearchBase1>YOUR SEARCH BASE</BDISearchBase1>
       <BDIConnectionUsername>[email protected]</BDIConnectionUsername>
        <BDIConnectionPassword>PASSWORD</BDIConnectionPassword>
        <BDIEnableTLS>0</BDIEnableTLS>
   </Directory>
</config>
For example, let´s assume the following:
- Domain controller IP address is 10.1.1.2 .
- Your presence domain is test.local .
- Your search base will be test.local using the top level of the domain.
- Your username with which you will be doing your searches is called walt . Usually you can either identify walt as test.local\walt or [email protected] . It is always best, in these sort of scenarios, to use the UPN convention so we will be configuring a [email protected] .
- The password is the Active Directory password for the account walt .
- I have disabled TLS in my case. There are issues with the Jabber for Mac client when using other security methods.
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
    <Directory>
        <DirectoryServerType>BDI</DirectoryServerType>
        <BDILDAPServerType>AD</BDILDAPServerType>
        <BDIPrimaryServerName>10.1.1.2</BDIPrimaryServerName>
        <BDIPresenceDomain>test.local</BDIPresenceDomain>
        <BDIServerPort1>3268</BDIServerPort1>
        <BDISearchBase1>DC=test,DC=local</BDISearchBase1>
       <BDIConnectionUsername>[email protected]</BDIConnectionUsername>
        <BDIConnectionPassword>walt01!</BDIConnectionPassword>
        <BDIEnableTLS>0</BDIEnableTLS>
   </Directory>
</config>
One you have configured the jabber-config.xml file, you will now need to upload it to you TFTP server. Once uploaded, you will need to restart the Cisco TFTP service. Again, my TFTP server is on my CUCM publisher, so:
- I go to Cisco Unified OS Administration on my Publisher server, TFTP File Management and I upload jabber-config.xml to / directory
- I then go to Cisco Unified Serviceability on my Publisher server, I locate the Cisco TFTP service and I restart the service
Once this is done, you can figure up your Jabber for Mac client. As a test, on your Mac (using Terminal) go to:
/Users/username/Library/Application Support/Cisco/Unified Communications/Jabber/Config
In here you will see several files, but what we want to see is jabber-config.xml . As soon as you start the Jabber for Mac client and log in, the jabber-config.xml file will download from your TFTP server and get saved here. When you see it appear, just type in your terminal window more jabber-config.xml and make sure that the output is the same as the xml file you created.
From there, try doing directory search. If you have previously added contacts and they still lack attribute information, you will need to remove them (sometimes it will not refresh properly) and add them again from the directory.
I will be updating this guide and ammending anything that is incorrect, but this is meant to be a quick checklist and steps to get this, at least in the most very basic version, up and running for Jabber for Mac.

Hello,
Thanks for this post! It works, I can do lookup and also I can add found contact to contact list and get information about contact from LDAP.
One more question: - I can't get all information about contact. I don't get e.c mobile phone number and more others attributes. I have tried to expand your file as follows:
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
<Directory>
<DirectoryServerType>BDI</DirectoryServerType>
<BDILDAPServerType>AD</BDILDAPServerType>
<BDIPrimaryServerName>IP of AD</BDIPrimaryServerName>
<BDIPresenceDomain>Presence Domain</BDIPresenceDomain>
<BDIServerPort1>3268</BDIServerPort1>
<BDISearchBase1> Search Base</BDISearchBase1>
<BDIConnectionUsername>User</BDIConnectionUsername>
<BDIConnectionPassword>Password</BDIConnectionPassword>
<BDIEnableTLS>0</BDIEnableTLS>
       <BDISipUri>msRTCSIP-PrimaryUserAddress</BDISipUri>
       <BDIPhotoSource>thumbnailPhoto</BDIPhotoSource>
       <BDIBusinessPhone>telephoneNumber</BDIBusinessPhone>
       <BDIMobilePhone>mobile</BDIMobilePhone>
       <BDIHomePhone>homePhone</BDIHomePhone>
       <BDIOtherPhone>otherTelephone</BDIOtherPhone>
       <BDITitle>title</BDITitle>
       <BDICompanyName>company</BDICompanyName>
<BDILocation>co</BDILocation>
<BDIPostalCode>postalCode</BDIPostalCode>
       <BDICity>l</BDICity>
       <BDIState>st</BDIState>
       <BDIStreetAddress>streetAddress</BDIStreetAddress>
</Directory>
</config>
But it didn't help.
When I capture lookup via Wireshark, I can see that Jabbers sends search request with bunch of attributes, but from LDAP answer contains only 8 attributes. (see attached screenshots)

Cisco Jabber for Mac, possible without a Presence Server?

Hi all,
is it possible to use the cisco jabber client for Mac without a presence server in the uc environment? A customer is looking for Voip Client/Softphone for their Apple Macs. Instant Messaging is no requirement.
Regards
Steffen

WIlliam,
I belive he could use a Webex Connect account, IPSec VPN, and a CSF device in CUCM to achieve what he is looking for. Though it is a shame that he would need to have Webex Connect to do this just to be able to login to Jabber...
FYI:
I just tried out the CUP integration with Jabber for Mac with my customer with CUCM 8.6.2(a), CUCXN 8.6.2(a), and CUP 8.6.1 HA. It seemed to work ok (I was using VPN as well). For some reason the directory service said it failed yet I could search for people in the directory and it worked fine (strange...). I think this may be because the XCP Directory Service on both CUP servers will not start (not sure why because I do not seem to need it).
My only complaint is that I originally had Jabber for Mac installed for Webex Connect integration. There appeared to me, that there was no way to re-run that original wizard (I looked all around in the package contents...) and select Cisco Presence instead of Webex Connect. To get around this I used AppCleaner to remove Jabber, re-download from Cisco, and re-install, this time selecting the Presence option. Once I tested I had to rinse-repeat to get my Webex Connect back because that is what we use internally. Hopefully they fix this because it makes it hard for us engineers to test Presence integration during installs.
Opinion on Jabber with Webex Connect:
I love it for creating Instant Meetings - It sends an email instantly to me that I can forward to attendee's right away (most of time not with contacts otherwise I would do it that way).
I love the new iPhone app that was just released as well. Very cool. (Do not like how you cannot be logged into both though, not a big deal, Archives of chats are my biggest concern). It is a pretty seemless login/logout from iPhone to Mac and Mac to iPhone though, which I appreciate.
I have no desire for Phone Services or Voicemail integration so it is annoying that it always says at the bottom of the buddy list "Server or port unreachable". I assume that you need to be connected to VPN in order to have connection to CUCM to use the CSF device... Jabber 8.6 Release Notes says that Jabber is not supported with NAT without VPN
Also the Chat History is weak on Mac, and none existent on iPhone . Would be cool if history was built in like CUPC or Lync, doesn't require going to Finder to view, and messages would archive on server.
Plus we use Exchange UM for our Voicemail so not sure how that would integrate with Webex Connect. I believe Exchange Voicemail in Jabber would work with Presence integration though (which is puzzling but I guess it is because you can do all of those XCP external integrations in CUP. However, don't get me started with CUP/Exchange calendar integration and CUP not supporting SAN certificates with multiple hostnames on Exchange...
Thanks for the info on X-Lite and Bria, I may try out these options. I have been using CIPC through VMWare Fusion and it worked quite well. I believe I needed to install Virtual Audio Cable for the sound to work correctly. I use it through Fusion's "Unity" function and it looks like it is native!
Just my 2 cents. Let me know what you think.
One more thing (SJ):
Check out this site for Mac Apps for Engineers:
http://ciscovoiceguru.com/2071/mac-app-cisco/comment-page-1/#comment-2760
Ryan

Cisco Jabber for Mac 9.2.1: slow to register with CUCM

Hi,
We have this specific problem on our Jabber for Mac 9.2.1 client only: the client takes 60 to 70 seconds to connect to CUCM (running 8.6.2) when it starts.
After Jabber registers with CUCM, there is no issue, it's just very slow to register.
Anybody getting the same behaviour? We have no such issue on previous versions of Jabber for Mac version 8 or Jabber for Windows version 9.
Thanks,
Fabrice

For those interested, I have the answer to my own question: if one of your configured DNS servers is not responding, Jabber 9.2.1 will delay registration to the phone services. This behaviour is seen only in this specifc version of Jabber, hopefully it will be fixed in the next release. Watch out if one of your DNS server goes offilne.
Fabrice

No Audio on either end Cisco Jabber for Windows over Cisco AnyConnect

Our telephony staff is replacing our aging/unsupported VoIP system with a Cisco system and as the network tech, I'm trying to get Jabber for Windows to work over our AnyConnect VPN client. Jabber to Cisco phone and Jabber to Jabber calls work fine within our LAN.
However, when I take a laptop to a separate internet connection and connect to the network via the VPN, I can't get any audio to pass across the system, in either direction. If I call a phone on our LAN using the Jabber client (via AnyConnect), the phone rings and when I answer it, it's just dead air on both ends. If I reverse the process, calling from the phone to the Jabber client, the same thing, Jabber client rings, but dead air both ways once I answer.
Things I can do from the laptop over the VPN connection:
I'm able to get to the phone's web interface using that same laptop.
I can ping the phone as well. In fact, the VPN profile I'm using has full access to the entire VoIP Vlan including all IP traffic (all ~65,000 ports).
Searching the address book also works fine. I can search for staff and it's pulling directly from our Active Directory environment.
Is there any special settings on the firewall that I need to setup to allow the voice traffic (which I assume is RTP traffic)? I tried to add a service policy for RTP traffic, but that didn't seem to work...unless I built it wrong.
Jabber for Windows - 10.6.0
Cisco Anyconnect - 3.1.06079
Cisco 5515-x ASA - 9.2

I was able to resolve this on my own. I thought that SIP traffic needed to be inspected via the global inspection policy in order for it to pass through the firewall. I ran into the same issue with ICMP traffic from an Anyconnect client to LAN devices. I had to enable ICMP in that policy for us to be able to ping LAN devices over the VPN tunnel. So when I saw that SIP was already being inspected by this policy, I moved on looking for other solutions. Then I stumbled deep within a Google search (almost hit the end of the Internet doing so) where someone mentioned that SIP shouldn’t be inspected by that policy. So I unchecked it and bam! Voice is now working over the anyconnect client to phones on the LAN.

Jabber for IPhone over AnyConnect VPN calls to SIP Gateway - One Way Audio

Hello,
I am wondering if anyone has seen this before. I have the latest version of Anyconnect for the IPhone and Jabber app, running on the newest version of CUCM 8.6 and Jabber 8.6.
The Jabber phone registers fine and I can make internal calls without an issue. I also can make external calls to H323 and HGCP PRI gateways without an issue. However, when I make a call from the Jabber client that goes out a SIP gateway and SIP trunk I get one way audio. I do not see any packets even trying to leave inside interface of the ASA headed toward the SIP trunk IP.
I've also verified that useing the same VPN profile I can make 2 way audio calls out the SIP trunk from a softphone running on windows.
Anyone have any ideas what could be the problem?
Thanks.

Hi,
try to disable early media on 180 under sip profile settings for jabber client.
HTH
Anas
please rate if itnis helpful
Sent from Cisco Technical Support Android App

Does Jabber for Mac 9.2.1 require jabber-xml.config?

Hello,
Does anybody know if new Jabber for Mac version 9.2.1 require a jabber-xml config file?
Users with this new version are complaining that they can't search on the directory and that usernames are not showing correctly on the contact list (they just see the username@domain instead).
Jabber for mac version 8.x works correctly as it has been doing for a while.
Regards.

Yes, the latest release along with the feature regression, requires the .xml file
Global configuration files
Global configuration files apply to all Cisco Jabber for Mac users. Cisco Jabber for Mac downloads the global configuration file from your TFTP server during the login sequence.
The default name for the global configuration file is jabber-config.xml.
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/jabber/mac/9.2.1/JABM_BK_CB0ACEBC_00_cisco-jabber-for-mac-installation_chapter_010.html
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

BE 3000 with Jabber (for Mac) and webex connect integration problems

Hi,
This is my first question on the forum so please be gentle!
I have a customer who has a Business Edition 3000 and they have purchased WebEx connect and Jabber integration to go with it.
My problem is I am having difficulty getting the setup to work and I have a number of questions on how to set this up. Most of the docs on Cisco's website seem to be related to either CUCME or full CUCM, but not a lot on BE 3000. My questions are below:
1. I have been reading the documentation for WebEx connect and it states to set the IP address of the BE 3000 server in the Configuration>Additional Services>Unified Communications>Voicemail tab. This is currently on the network with a 192.168.x.x address however. My predecessor put this IP address in the WebEx configuration page but I'm not sure this will work with a private IP as I don't know how this communicates back. The documentation isn't very clear on this. Does this have to be a public IP address / FQDN for it to work?
2. Are there any SRNDs for this type of setup that could help? Again, looking through the website hasn't turned anything up yet.
Note:
we are using the following software:
Jabber for MAC:
uc-client-mac-8.6.7.20127.fcs.zip
MAC OS:
OSX 10.8.3
BE 3000:
MCS7890C1-BE8
8.6.4.10000-15.
Thanks in advance for any help.
Regards,
Jason

Hi - I have done this via the admin portal but still cannot get the Jabber client for Mac to register for voice. The Windows version works fine for the same user and CUCM device. Are there any other settings that need to be enabled specific to the Mac client?
Thanks.

Contacts search for cisco Jabber for Windows & MAC

Hello,
Please assist on given below query !!
System Deatails of CUCM & IM Presence Server
CUCM:
1> System version: 9.1.1.20000-5
2> VMware Installation: 2 vCPU Intel(R) Xeon(R) CPU X5650 @ 2.67GHz, disk 1: 80Gbytes, 4096Mbytes RAM
3> Physical Server UCS210 M2
4> Already Integrated with IM & Presence
IM & Presence:
1> System version: 9.1.1.20000-5
2> VMware Installation: 1 vCPU Intel(R) Xeon(R) CPU X5650 @ 2.67GHz, disk 1: 80Gbytes, 2048Mbytes RAM
3> Physical Server UCS210 M2
4> Already Integrated with CUCM
Requirement:
1> User Search base for Cisco Jabber for Windows & MAC Client
2> Will we able to get contacts list(Jabber For windows & MAC) as like "Lotus Sametimes" for all users?
Every reply would highly Appreciated!!

Hi Karthik,
Thanks for your reply!
I have gone through the link but query is different actually, please assist on below query and provide any document links if possible.
1> The contacts does not appear when I perform a search
2> Do I required to integrate LDAP for same? If Yes Then Do I need to perform integration with CUCM Or IM & Presence? Or Only CUCM? Or only IM & Presence? (Please post a link to perform same)
3> Please also provide If any specific system requirement for LDAP server.
4> Is it possible without LDAP integration?
It is really urgent and every post would highly appreciate..........

Jabber for Mac 9.2.1 Cannot communicate with the server

Hi All,
I'm using Webex and the Jabber for Mac 9.2.1 client that was automatically pushed. I see "Cannot communicate with the server" when I attempt to login.
The same credentials work correctly when using the 8.6.5 client version. I've attached the problem report file.
I would appreciate some guidance on what I need to do to get this to work.
Cheers,
Steve

We've seen this with a few of our users as well. All started noticing having issues Friday morning. As this is a hosted service for us via webex we had our engineers call in to Jabber support. Cisco performed a modification to their account and they were able to connect again. No SRV records were messed with.
***EDIT*** - This appears to have been caused by a certificate issue. The Trusted Root Certificate for QuoVadis expired and was not renewed on some machines.
Go here: https://www.quovadisglobal.com/QVRepository/DownloadRootsAndCRL.aspx
Install the Cert for : QuoVadis Root CA2 (in windows, download as DER>right click file>install)
Jabber should connect now. The issue was in SSL validation with the appropriate hosted servers.

Cisco Jabber for Windows always shows "Away"

Cisco Jabber for Windows (9.0.1, CUPS 8.6.4, UCM 8.6.2, Exchange 2010) always shows status as "Away" for one user. Others seem to be working correctly showing "one the phone", "in a meeting", etc. Tried reinstalling client with no change. If you manually change to "Available", it changes right back to "Away". Anyone have an idea where to look (registry, logs, etc.)?

I am seeing the same problem. I haven't tried a different user to login on the same machine, but I did try closing my client on my primary machine (exited) and then logged in on a different computer with a fresh Jabber for Windows install.
I am running Jabber for Windows Version 9.0.2 Build 9453 on windows 7 64bit primarily, and Windows XP as the second test. Running CUPS 8.6.4 in HA over WAN cluster mode with CUCM 7.1.5 and Unity Connection 8.5.1 ES 16.
Phone presence information does still flow through when I pick up my phone hand set my status changes from Away to On a Call.
When I check the presence diagnostic test for my user, it also reports that I am away.

Cisco Jabber for Windows Client SDK

Is there an SDK for Cisco Jabber for Windows client? I could only find the Web SDK. Are there no other SDKs that would let me control features of the Jabber Windows Client?

And in order to avoid TAPI limitation, they say they have started using Jabber which controls all phone functionalities through an Application User connected to the Call Manager.
Assuming they are referring to the normal Jabber for Windows/Mac/iOS/Android applications then this is wrong. Jabber - the client, not the IM&P servers which are part of the CUCM cluster (if you're familiar with Lync consider CUCM+IM&P servers a Front End Pool) - do not use an Application User at all. When a user starts Jabber, assuming SAML SSO is off, they supply an email address. This is used to find the servers via DNS SRV records, or the Mobile and Remote Access Expressway (roughly analogous to a Lync Edge pool) to tunnel through the firewall. After the email address they are prompted for their End User username and password. This is then used to access several APIs on the server, namely the User Data Service to discover what the user has. This would include what the user has configured/available to them. After this is done the Jabber client does one of three things with respect to phone functionality:
If the user has no phone devices provisioned for them - physical or software - it becomes an IM&P client only.
If the user has a software phone phone provisioned, it registers as that using SIP. In this way Jabber is the actual phone. This is called a CSF device for Jabber Windows/OS X.
If the user has a desk phone assigned to their End User account AND administrative policy is to default to desk phone control, it registers to CTI Manager on the CUCM server to control the user's physical phone.
A user can toggle between option two and three, if appropriately provisioned, but cannot have both simultaneously. In other words, Jabber is either controlling a physical phone over CTI or is a phone itself using SIP. The difference is where the audio/video media is sent from/to.
All of this happens using that human's End User credentials.
Now, if you wanted to have a server control the user's phone - either a physical one or Jabber - you would use the TSP as an interface to CTI Manager on the CUCM server and receive real-time events (e.g. the user went off-hook, the phone is ringing with this caller ID, etc.) and issue commands to that phone (e.g. make a call to X). This is done using an Application User account because the server would need to do this for multiple users simultaneously. If you also use the Super Provider concept, the CUCM administrator doesn't have to take the extra step of associating every phone to your Application User manually. Instead, you can simply issue CTI subscriptions to see any/all device activity you want.
This is all assuming you wanted to do the integration server-side to avoid having to update the Cisco TSP application on every user PC (which also limits your WPF application to machines capable of running the TSP) every time the CUCM administrator patches the servers. If you don't care about that, then you can do this all client-side on the user's PC, and have them supply their End User credentials.
Of course, you could also reconsider the Jabber SDK and just embed the make/receive call functionality directly into your application instead.

Call/video not working between Cisco jabber for Windows and VCS control C40s

Hello,
I've been struggling with no luck how to make a call using Cisco Jabber for Windows 9.6.0 registered to CM 8.6.2 with intercluster ICT to another CM 8.6.2 where we have a VCS Control 7.0.2 via GK H225, and all C40s are registered as H.323.
The VCS has interworking between H323 and SIP, however not sure if there is any problem with that. Assuming it is ok, not sure either if I'm facing any interoperability issue because in my remote site I have C40 (H323 registered at VCS and SIP listening mode) and cisco jabber for windows which is SIP based.
If is not possible, would I be able to change my C40 from H323 to SIP at VCS, or have both H323/SIP registered at VCS? If so, will I need to change as well instead of GK I'll have to establish a SIP Trunk between the CM and VCS?
Another thing I do not believe either I would be able to have one VCS connected with two clusters, right?
I'm just trying to find a solution in case my current topology is not compatible, but feel free if you have any better idea to make it work.
Anyway here is what is happening:
When I make a call from my cisco jabber windows to C40 using alias number. The call is being redirected just fine to the C40 and it rings, however when someoene or the auto answer picks it up, the call dropped right away.
However, if I enabled the MTP in my CSF device, the call gets longer before dropping. I was even able to see my jabber " start video" turns green, before was grayed out all the time and the call dropped faster. I hear a fast busy tone.
I'm able to provide SDI traces, logs, diagnostic sip/h323 calls from VCS in order to know for sure if this is an incompatible issue or something I can workaround.
Let me know if someone of you are interested in read these logs or could point me on the right direction.
Thanks!

Ok,
I have looked at both logs. I have to mentinon though that you didnt
provide the log that shows the h323 setup between cucm and the VCS. This
is most likely because the call originated from a different cucm than
the ones you provided the logs from.
The call would have orginated from the first cucm in the cucm group of
this trunk: Name=RL_TRUNK_VIDEO
The cucm ip will be : 10.252.53.10.
This is the VCS log that confirms where the h323 request originated
from:
pr 10 22:50:29 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:29,187"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="54000"
Received RAS PDU:
Having said that here is my analysis of the logs that you sent..
Jabber sent an INVITE to CUCM and advertised all the codecs (audio and
video it can support)..
Observer that Jabber says it doesnt support G729 anexB
21:55:16.576 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message
from 10.223.20.73 on port 54677 index 90661 with 2220 bytes:
[862370,NET]
INVITE sip:[email protected];user=phone SIP/2.0
Via: SIP/2.0/TCP 10.223.20.73:54677;branch=z9hG4bK000029d3
From: "4122107" <sip:[email protected]>;tag=00059a3c78000011000070b0
-00000e65
To: <sip:[email protected]>
Call-ID: [email protected]
Max-Forwards: 70
Date: Fri, 11 Apr 2014 01:55:16 GMT
CSeq: 101 INVITE
User-Agent: Cisco-CSF/9.4.1
m=audio 19252 RTP/AVP 0 8 18 105 104 101
c=IN IP4 10.223.20.73
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:105 G7221/16000
a=fmtp:105 bitrate=24000
a=rtpmap:104 G7221/16000
a=fmtp:104 bitrate=32000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
m=video 28878 RTP/AVP 97
c=IN IP4 10.223.20.73
++++Now lets observer the capabilites exchange during h245 negotiation
between cucm and VCS++++
Here CUCM advertises its caps to VCS (afterreceiving caps from VCS)
Note that G729A, G729AB, G729 is all advertised..
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,017"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="45660"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= request : terminalCapabilitySet
capabilityTableEntryNumber 2,
       capability receiveAudioCapability :
g729wAnnexB : 6
       capabilityTableEntryNumber 3,
   capability receiveAudioCapability : g729AnnexAwAnnexB : 6
       capabilityTableEntryNumber 4,
       capability
receiveAudioCapability : g729 : 6
capabilityTableEntryNumber 5,
       capability receiveAudioCapability :
g729AnnexA : 6
++++++
After doing MSD (master slave determination, we move to the OLC phas e..
Here we see that the far end..c40 wants to use G729AB for media++++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,783"
Module="network.h323" Level="DEBUG": Src-ip="10.224.114.11" Src-
port="11163"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= request : openLogicalChannel :
   forwardLogicalChannelNumber 1,
forwardLogicalChannelParameters
     dataType audioData :
g729AnnexAwAnnexB : 20,
     multiplexParameters
h2250LogicalChannelParameters :
+++Next VCS sends G729AB as the codec to use to CUCM+++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,784"
Module="network.h323" Level="DEBUG": Dst-ip="10.252.53.10" Dst-
port="45660"
Sending H.245 PDU:
value MultimediaSystemControlMessage
::= request : openLogicalChannel :
   forwardLogicalChannelNumber 1,
forwardLogicalChannelParameters
     dataType audioData :
g729AnnexAwAnnexB : 20,
     multiplexParameters
h2250LogicalChannelParameters :
++++The next thing we get is an OLC reject from CUCM and this is where
th call drops++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,790"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="45660"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= response : openLogicalChannelReject :
forwardLogicalChannelNumber 1,
   cause dataTypeNotSupported : NULL
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,790"
Module="network.h323" Level="INFO": Dst-ip="10.224.114.11" Dst-
port="11163"
Detail="Sending H.245 OpenLogicalChannelRejResponse
+++We then receive a call release from cucm with cause code of 47:
resource unavailable++++
Apr 10 22:50:32 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:32,365"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="50913"
Received H.225 PDU:
Q931
   Message Type: Release
Complete
   Call reference flag: Message sent from originating side
Call reference value: 0x7b
   Info Element : Cause
     Location: Usr
   Cause Value: Resource unavailable
   Info Element : User User
   Length = 22
Suggestions:
Change the region setting between the ICT trunk to VCS and Jabber to use
G711 and test again.

Configure Jabber for Mac with local CUCM and WebEx Connect

Hi, I was wondering if anyone has been able to configure the Jabber for Mac 8.6.2 client to use the WebEx Connect presence server with a local CUCM and Unity Connection servers. The preferences accounts tab does not show or allow the addition of the voice services. I have added from a working local CUCM preferences plist file what I believe are the correct entries however I still cannot see the accounts on the preferences tab. We currently do not have a local cisco presence server hence the requirement to trial the WebEx Connect server as I can't get past the first configuration step without it.
regards
paul

Hi - I have done this via the admin portal but still cannot get the Jabber client for Mac to register for voice. The Windows version works fine for the same user and CUCM device. Are there any other settings that need to be enabled specific to the Mac client?
Thanks.

Jabber for Mac CTI DX650 issues

Hello,
I have a user who had Jabber for Mac setup using CTI for control of a 7942. Everything was working, then we switched it out with a DX650. Made all the changes needed in Call Manager same as some other users. However, it will not connect to the DX650 for this one user. We have checked all the roles and ownership tracking for the phone to the user account and it appears to be setup correctly, however it will not connect. Anyone have this setup that could help? Trying to figure out if I am missing something magical that Cisco added in.
Thanks

Can you confirm that under cucm admin \ user management\ end user configuration section; do you have the following permissions incorporated for this test user;
Standard CTI Allow Control of Phones supporting Connected Xfer and conf
Standard CTI Allow Control of Phones supporting Rollover Mode
If not can you include the same for this end user and then retest the CTI control.
- please rate if this helps.

Cisco jabber for mac over fortigate vpn problem

Similar Messages

Maybe you are looking for