Cisco Jabber and Voicemail

Hi
I have CUPS, CUC and CUCM in HQ. And rest of my Branches have SRST routers which have local cisco unity express for voicemail;s but ip phone numbers are from cucm in hq.
Now HQ users get to see their voicemail messages in their Windows Jabber, but branch users dont get to see their voicemail on windows jabber.
Although voice mail ports are configured on cucm for branch cisco unity express, and voice mail works fine for branches but how do we integrate cisco unity express with presence server.
Now on cucm, under user management-> user setting->service profile, only profiles which are there are for cisoc unity connection.
Can somebody tell me how do we get voicemail of cisco unity express users on windows jabber.
Thanks and regards
Vibha

Hi Vibha,
Unity express is not supported for voicemail integration for jabber. You can refer the below:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/10_5/rn/JABW_BK_J559CFFB_00_jabber-windows-release-notes-10-5/JABW_BK_J559CFFB_00_jabber-windows-release-notes-10-5_chapter_01.html#JABW_RF_SB575AAA_00
Regards

Similar Messages

Jabber and Voicemail Notifications

Hello guys!
Is it possible to receive voicemail notification on both jabber and desk phone at the same time? For example, if a user has a desk phone as primary extension on CUCM 8.6, the Unity use that extension for VM. But if the user has also a jabber client version 9.x for Windows and wants to receive voicemail on jabber, what is the best design option? Assign the same DN to both jabber and desk phone?
Also, I set up visual voicemail for jabber but left a voicemail in jabber and no notification appeared, where should i look into? The voicemail server and profile with users were added in CUP.
Note: The scenario is a BE6000 platform with CUCM8.6, CUCxN,8.6, CUP8.6 and CUPM8.6.
Thanks in advanced!

Why would you have different extensions on desk phone vs. jabber? Normally this is not desired for user to manage 2 different numbers.
If however that is a requirement you can always define alternate extension on Unity Connection.
For VM configuration did you configure all the service in CUPS server, i.e. mailstore?
HTH,
Chris

Jabber and Voicemail Access

Hello,
I've configured CUCM and IM&P v9.1 and jabber client 9.2(1), the chat and the calls work fine but when I try to log in Phone Accounts -> Voicemail I get an error about the credentials, I have all integrated with Active Directory and the user and password that I'm using for voicemail is the same that I use to log in the jabber client wich worked fine.
Here I attached the error screen.
What do you think can be causing this??
Thanks in advance.

Hi every body,
I have some problems but not with all the users, is only working with 3 users and the rest of them don't work, I attached the errors that I get when I try to log in Telephony Accounts in the Jabber, I used the Jabber of one User, and from here I introduce my credentials (user and password) and I can get the voice mails (only from de 3 users that is woriking fine), but when I introduce the credentials of the other user I get the error and Can't get the voicemails.
The 127.23.0.7 is the IP address of the Cisco Unity Connection.
Please Help Me I'm stuck with this!

Cisco Jabber for Windows Voicemail issue

At this I'm in processing of implementation Cisco Jabber UC solution for big Company.
I use CUCM 9.1.2, Cisco IM and Presence 9.1.2, CUC 9.1.2, Cisco Jabber for Windows 9.6.1.
I have issue in Cisco Jabber with VoiceMail Integration - when I leave voice message for any user,
than this message is arrived only him Cisco IP Phone, but not in him Cisco Jabber.
From Cisco Jabber Connectivity status in help menu I see that VoiceMail service is successfully connected
and I see VoiceMail button in Cisco Jabber.
How can I resolve this issue?

Have you configured the UC Service profile on CUCM with both Voicemail server and mailbox servers?

Jabber and Desk Phone Integration

When stting up "Desk Phone Integration" on cisco Jabber on a test iPhone, Jabber loops forever when verifying account information saying just "verifying...". It never display an error message. It will eventually stop, the "Desk Phone Integration" staying "Not Configured"
CUCM version : 8.6(2)
iPhone iOS : 6.0.1
Jabber client : 9.0.2.20078
I followed the instructions in the "Administration Guide for Cisco Jabber for iPhone Release 9.0.1" to setup the call manager.
I created a dedicated SIP profile,
created the TCTTEST "Cisco Dual Mode for iPhone" phone according to the documentation
and edit my phone and user settings according to the "Enable Active Call Transfer Between Cisco Jabber and Desk Phone" section of the documentation
despite all that, it doesn't work
I tried with other accounts/mobiles and the result is the same.
Jabber does register to the CUCM and I can get my extension on the Jabber client and place/receive calls using my desk extension. But the "desk phone integration" doesn't work
What I noticed is that :
on the TCTXXXX "Cisco Dual Mode for iPhone" phone device setting page, there is no "Sign In Feature" option as described in the documentation
because we use Extension mobility the "Owner User ID" feature is disable on the desk phone device settings. I temporarily uncecked the "extension mobility" checkbox on the device, setup my ID as the "Owner User ID" and re-checked the "extension mobility" checkbox but the result is the same.
I searched the web and couldn't find anyone with similar issue...help will be appreciated

Aaron,
Thanks for you answer.
I have followed all the requirements explained in the "Administration Guide for Cisco Jabber for iPhone Release 9.0.1" including the one you mentioned :
the user is a member of 'Standard CTI Enabled'
CTI Controlled is allowed on the DN, the end user account and the desk phone
the end user is associated to both the desk phone and the TCT phone
And 'Allow End User Configuration Editing' is set to disable on the TCTxxxx device
Despite all that the "desk phone integration" doesn't work

Cisco Jabber v. 10.5.0 Build 37889

Does Cisco Jabber v.10.5.0 (Build 37889) offer a "View Conversation History" feature as did v. 8.5.1.17660-6.1.34?
This is a critical feature that I'm unable to locate in the 10.5.0 version. Am I overlooking the location of the "View Conversation History" feature?
Thank you,

Hi Shaun-
I don't recall if this was in 10.5, but it is in 10.6. You can edit the jabber-config-defualts.xml file located in C:\Program Files (x86)\Cisco Systems\Cisco Jabber and update the EnableAutosave element to TRUE:
<userConfig name="EnableAutosave" value="TRUE"/>
After that is completed your conversations will live in C:\Users\<username>\Documents\MyJabberChats as HTML files.
If you want to get really crazy you can also have the conversations pushed to exchange:

<userConfig name="EnableSaveChatHistoryToExchange" value="TRUE"/>
<userConfig name="ExchangeAuthenticateWithSystemAccount" value="TRUE"/>
<userConfig name="archive_im_on_exchange" value="TRUE"/>
If you update this the conversations will be placed into the folder in Outlook called "Cisco Jabber Chats"
The conversation will be saved / sent to Exchange once you close the chat session. You will need to restart jabber before the changes take effect.
Again- I'm not certain if these features are in 10.5 or if Cisco will even provide support for them, but I have them both set up and so far they are working great. The only issue I have found is if you kill the Jabber application any chat that hasn't been saved will be lost. Not a big deal, but something to be aware of.
DJ

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)

Cannot login to Cisco Jabber 10.5.1 over Mobile and Remote Access

Hi,
We have deployed sucessfully VCS Expressway-C and VCS Expressway-E with only 1 zone which is "Unified Communication Traversal" and is for Mobile and Remote Access only. VCS-C and VCS-E are communicating and in statuses everything is active and working. Also VCS-C can communicate with CUCM and CUP (both version 10.5).
Problem is when I deploy Cisco Jabber 10.5.1 on computer outside of LAN and without VPN it start communicating with VCS-E, ask me for accepting certificate (we have certificate only intenally generated on Windows CA) and after that it is trying to connect and after few seconds it will tell me that it can't communicate with server.
Did any of you had same problem or can you advice how to troubleshoot? In Jabber logs there is only something like "Cannot authenticate" error message, but when I startup VPN I can authenticate without any problems.
Thanks

On Expressway-C are your HTTP Allow Lists setup properly? By default, and auto discovered CUCM and IMP should be listed via IP and Hostname, but if not, you'll need to insert manually.
Also, you can look at the config file your Expressway-E would be handing out to Jabber via this method.
From the internet, browse to:
https://vcse.yourdomain.com:8443/Y29sbGFiLmNvbQ/get_edge_config?service_name=_cisco-uds&service_name=_cuplogin
Where:
vcse is your Expressway-E hostname (or CNAME/A record)
yourdomain.com is your own domain
The first directory is your Base64 encoded domain name, remove and trailing equal signs (=)
The XML returned is basically the DNS SRV record information available as if internal for _cisco-uds and _cuplogin
TFTP DNS SRV is optional if you configured TFTP in IMP for your Legacy Clients.

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.

CISCO Jabber 8.6.2 and CME 8.6

Hello,
I want to use Cisco Jabber 8.6.2 with Call manager Express 8.6
I configured the IPhone on CME and is working ok on local wireless LAN,
When I’m using the VPN I can place call's inside the network but I can't use on outside line. I have no sound.
Also if I place a call and the I end the call, the called phone rings and is not stopping. So I think is a call disconnect problem.
Bellow is a part of the configuration.
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
h323
call start slow
sip
session transport tcp
registrar server
voice class codec 1
codec preference 1 g729r8
voice class custom-cptone romania
dualtone busy
frequency 450
cadence 170 170
dualtone disconnect
frequency 450
cadence 170 170
voice register global
mode cme
source-address 10.12.4.252 port 5060
max-dn 10
max-pool 10
authenticate register
hold-alert
tftp-path flash:
create profile sync 0000545624458818
voice register dn 1
number 5146
call-forward b2bua all 5108
call-forward b2bua busy 5160
call-forward b2bua noan 5160 timeout 18
name Ioan Stanciu
shared-line
label Ioan
voice register pool 10
registration-timer max 720 min 660
id mac 68A8.6D91.3FE0
session-transport tcp
type CiscoMobile-iOS
number 1 dn 1
username 5146 password 5146
voice-port 0/0/0
supervisory disconnect dualtone mid-call
supervisory custom-cptone romania
no battery-reversal
timeouts call-disconnect 2
timeouts wait-release 2
connection plar opx immediate 5150
caller-id enable
voice-port 0/0/1
supervisory disconnect dualtone mid-call
supervisory custom-cptone romania
no battery-reversal
timeouts call-disconnect 2
timeouts wait-release 2
connection plar opx immediate 5150
caller-id enable
dspfarm profile 1 conference
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec g729r8
codec g729br8
codec g722-64
maximum sessions 1
associate application SCCP
dial-peer voice 2 pots
preference 2
destination-pattern 9T
incoming called-number .
direct-inward-dial
port 0/0/1
telephony-service
video
maximum bit-rate 256
no auto-reg-ephone
em logout 0:0 0:0 0:0
max-ephones 25
max-dn 120
ip source-address 10.12.4.252 port 2000
max-redirect 7
auto assign 1 to 8
service phone videoCapability 1
service phone paramEdibility 1
no service directed-pickup
timeouts interdigit 6
timeouts ringing 15
Any idea what can be the problem ?

Hello,
Is the connect over 3G enabled on your iPhone? Try this.
Btw, what have you put as device ID on your iPhone? the MAC address?
To my knowledge, the device ID is TCTXXX for CUCM, there is no info related on how to add it for CME 8.6
Regards

Cisco Jabber for Windows in Extend and Connect mode and making outbound calls

Hi guys,
I've set up Cisco Jabber for Windows to use Extend and Connect to control a remote PBX endpoint. I've configured the required CTI-RD device, remote destinations, associated the users to the line and added the devices to end-user controlled device. The extend and connect part is working flawlessly without any issues. I'm able to receive inbound calls on the remote PBX endpoint and control the call (hold, resume, transfer etc.) using the Jabber call window that pops up.
However, I'm unable to make any outbound calls via the Jabber client when in extend and Connect mode. Reading the Extend and Connect guide, I need to configure Dial Via Office (DVO) Reverse. So when the user initiates a Dial-Via-Office reverse call, CUCM calls and connect to the Extend and Connect device (CTI-RD). CUCM then calls and connects to the number the user dialled and finally connects the two call legs.
After attempting to configure DVO-R for Jabber for Windows in Extend and Connect mode following the CUCM feature services guide, i'm unable to get any outbound calls working. From RTMT, i am receiving the following Termination Cause Code: (27) Destination out of order. What i also notice is that there is no calling number for that trace either. I would've thought that the calling party would've been the Enterprise Feature Access (EFA) number.
Has anyone got this working or can provide some guidance?
Thanks.

Hi guys,
I've set up Cisco Jabber for Windows to use Extend and Connect to control a remote PBX endpoint. I've configured the required CTI-RD device, remote destinations, associated the users to the line and added the devices to end-user controlled device. The extend and connect part is working flawlessly without any issues. I'm able to receive inbound calls on the remote PBX endpoint and control the call (hold, resume, transfer etc.) using the Jabber call window that pops up.
However, I'm unable to make any outbound calls via the Jabber client when in extend and Connect mode. Reading the Extend and Connect guide, I need to configure Dial Via Office (DVO) Reverse. So when the user initiates a Dial-Via-Office reverse call, CUCM calls and connect to the Extend and Connect device (CTI-RD). CUCM then calls and connects to the number the user dialled and finally connects the two call legs.
After attempting to configure DVO-R for Jabber for Windows in Extend and Connect mode following the CUCM feature services guide, i'm unable to get any outbound calls working. From RTMT, i am receiving the following Termination Cause Code: (27) Destination out of order. What i also notice is that there is no calling number for that trace either. I would've thought that the calling party would've been the Enterprise Feature Access (EFA) number.
Has anyone got this working or can provide some guidance?
Thanks.

Transfer VOIP Calls Between Cisco Desk Phone and Cisco Jabber For IPhone 9.5

Does anyone know how to transfer an active voip call from a Cisco IP Desk Phone to Cisco Jabber for IPhone? I can transfer a call from Cisco Jabber for IPhone to my Cisco IP Desk Phone no problem. I put the call on hold and then click "Resume" on my Cisco IP Desk Phone. However I cannot do the same but the other way around. If I put the call on hold on my Cisco IP Desk Phone, I see "no active call" on my Jabber client. The only information I could find slighlty relevant was using the Mobility Key/Remote Destination Profile feature however this defeats the object as this will forward to an external number, e.g. mobile and I just want to transfer the call within the VOIP environment between the two devices that are using the same directory number.
I am using Cisco Call Manager 9.1(2), Cisco Presence 9.1 and Cisco Jabber for IPhone 9.5.
Any help would be greatly appreciated.
Kind Regards,
Paul Parker.

Did you ever find an answer to this ?
I am seeing the same behavior and trying so see if I can put calls on hold and pick them up both ways also.
The only answer I seem to have found is to use park instead
That would/should work but I would just prefer to hold/unhold
Just not sure why we would not be able to hold/unhold on what is essentially a "shared" line
Does anyone have this working for them ?

MBA (mid 2013) and Cisco Jabber Video client not recognising any camera

The Cisco Jabber Video client is not recognising the internal Facetime HD camera nor the external USB Logitech Webcam C920.
This was not working from the beginning. Cisco is aware of this issue and promised to deliver a fix in the next release of their software.
After installing the 10.8.5 Update from App Store and the 10.8.5 Supplemental update the Cisco client was able to recognize the external camera.
After that I followed a hint to install the Combo update this should enable Skype to recognise the Facetime HD camera. After installing the Combo update Skype was able to recognize the internal and external camera (by the way the quality of preview video using Facetime HD was brilliant and much better than the internal camera of a MBA from 2012). BUT after that update the Cisco client was no longer recognising a camera.
I run a recovery installation of 10.8.4 - but the result was again a 10.8.5. If I try now to run a recovery install I only get a recovery of version 10.8.5 offered.
I did a SMC reset, a parameter RAM reset, tried to start in saved mode but nothing helped.
Any other ideas how to get a least an external camera working again with Cisco Jabber Video?

Similar problem here. I have a Logitech C615 camera/microphone plugged into my MAC mini running OSX 10.9.3. Today, JABBER could not find the camera (although it found the microphone?). I was running 4.5.7 and so downloaded v4.8.6 and reinstalled: no camera. I also downloaded the cloud version: no camera.
I was not running either Vidyo or Polycom RealPresence at the same time as JABBER
But, when I did run these apps, my camera & microphone both work.
Suggestions?
John

Differences between Cisco Jabber 9.2.6 and Cisco Jabber 9.7.1 for windows 7 PC?

It could cover the features or technical aspects of Cisco Jabber

Currently our users are using Cisco Jabber 9.2.6, while we are planning to move to 9.7.1...
Looking for a simplified way to explain the difference to the users.

Cisco Jabber for Android on a Samsung Galaxy Xcover (GT-S5690)

Hello there,
Yesterday we installed the Cisco Jabber client for Android on the Samsung Galaxy Xcover (GT-S5690) phone.
First we had some issue's with one-way voice, but suddenly this problem was occured.
Another problem, which is still there, is when you wants to check your compagny Voicemail (Unity) with the Cisco Jabber client.
We can access the Voicemail system (Unity), the we must fill-in the pincode followed by hash.
As you can see in the attached file, this can't be done.
Samsung Galaxy xCover (GT-S5690)
Samsung Galaxy S2
The reason is the screen size of the display of the difference of the phones.
Hopefully can this small issue be fixed. Our customer ordered 150x Samsung Galaxy XCOVER (GT-S5690) for working with Cisco Callmanager.
Technical Information:
Cisco Callmanager version 8.6.20000
Samsung Galaxy XCover (GT-S5690)
Android version: 2.3.6
If someone knows a solution of can support me, please let me kwon!
Kind regards,
Edgar Verbaten
Elkor Telecom & ICT
[email protected]

Hi Edgar
How does this phone work with the Jabber ?
I have a customer which about a dozen of these phones and it only vibrates on incoming calls but doesn't ring.
Same Android version : 2.3.6 -
Regards
Andri

Cisco Jabber and Voicemail

Similar Messages

Maybe you are looking for