Unity Sign-in Greeting

We are a Unity 7.0 shop. We would like to customize the Unity Sign-in greeting where the electronic voice says "Enter your ID, followed by #". We have quite a bit of turnover and our Helpdesk always receives calls about users being confused about what the ID means. We have documentation that we provide that says to enter your extension, but still this ID recording causes confusion.
Is there a way to re-record that Sign in prompt? We haven't found a way to do it. Any help would be appreciated.                  

We are a Unity 7.0 shop. We would like to customize the Unity Sign-in greeting where the electronic voice says "Enter your ID, followed by #". We have quite a bit of turnover and our Helpdesk always receives calls about users being confused about what the ID means. We have documentation that we provide that says to enter your extension, but still this ID recording causes confusion.
Is there a way to re-record that Sign in prompt? We haven't found a way to do it. Any help would be appreciated.                  

Similar Messages

  • Unity 7 Alternate Greeting - auto enabled

    Hi,
    I have just migrated 1600 users via COBRAS from Unity 4.0.5 to Untiy 7.0 and I seem to have an issue whereby users complain their Alternate Greeting is enabled when they have not enabled it themselves.
    Has anybody experienced this issue, anybody aware of a bug in this area?
    Is there a way for me to check audit logs to see if this is getting set by an administrator (unlikely) or the end user? I assume this will be or could be enabled to be logged somewhere.
    Thanks
    Jed

    yeah, if you're updating the switch Id it has to touch the contact (transfer) rules since it's legal for those to be associated with different phone systes (though highly unusual).  If there's no note about updating the greeting rule for alternate for any of the logs then BulkEdit isn't likely your culprit.
    IF there's nothing in the IIS logs (where the administration web inteterface does it's logging) that the admin reports pull from and BulkEdit isn't your guy then there's not a lot of good ways to run down who made this change or why - someone could, of course, had done direct DB edits (using SQL manager, the CLI or CUDLE among others) - Audio Text Manager could have been used (doubtful - it's a one-at-a-time type interface, too, just as the SA is). 
    Unity doesn't have a full audit log at the SQL level (this was tried but it bogged MSSQL down way too much to have that level of table/row based log output) - Connection has something like this (done at the trigger/proc level) so you can back trace how a change was made (though not always who changed it) but so far as I know Unity has nothing this deep for root cause analysis of such changes.

  • Cisco Unity Connection, personnal greeting is not getting played

    Hi,
    In CUC 8.0.3, for my extension I enabled "Alternate Greeting" with my personal recording.  After when i test dial the number's voice mail (from DN call forward all to VM), system plays the Alternate greeting with system's default greeting (i.e. the extension <ext.no> is not available...)  instead my personal recording.  However when I check the VM box settings it tells my current greeting is Alternate Greeting followed by my personal recorded message.  Also in the CUC page (users ->  Edit greeting (alternate)) also " My Personal Recording" option is choosen.
    Could anyone pelase suggest if any other configurations I need to check?

    Hi All,
    Just to update,   Earlier I recorded in English (United States, option 2), when I try to record a greeting in English (United Kingdom, option 9) it works and the sytem playes the correct personal recording message (Alternate greeting).
    In the server's system settings -> general configuration, system default language (&TTS language) is set to English (UK), Recording Format is g.711 mu-law.
    Now again I tried overwriting the Alternate greeting in different language but still only the English (UK) greeting is played.  I tried changing language setting in the Edit User Basics page and in the Alternate greeting's page but it doesn't help.
    But when I test it in media master I can hear all the recorded greetings based on the language is selected.  So does it confirm it is due to codec issue?
    Regards,
    Durai

  • Variable Length Digit Input CVP

    So basically I want to make something that says.
    "if you have your account number please enter it now or if you don't have it press the * to continue".
    Same thing on some of my menu's
    "Welcome to blah blah, for 1 press 1, for 2 press 2, or if you know your parties 6 digit extension please Enter it now". What is the best way to accomplish this with CVP?
    Chad

    Chad, here's my 2 cents.
    Resist the tempatation to do it that way. You don't get the automatic length checking and all the other good things that come from entering fixed length strings; and you can make CVP handoff to Unity handlers that do functions like dial by extension much better.
    A lot of that crap came from a variety of proprietary PBX and voice mail systems. "Star" on one system means "continue" and means something else on another system.
    Try to standardize along the lines of VXML.
    Provide clear and unambiguous menus that have less than 5 options. Avoid the "... or stay on the line for customer service" option.
    Something like ...
    "If you know your 8 digit account number, press 1.
    Otherwise, press 2".
    If they choose 1, you can have a fixed length "get digits". Self checking and all that good stuff.
    And then in another menu of yours ...
    "For the auto-attendant, press 1.
    For xx, press 2.
    For yy, press 3."
    Then in auto-attendant ...
    "If you know your party's extension, press 1 (leads to a Unity dial by extension handler)
    To dial by name, press 2.
    To check your voice mail, press 3.
    (2 leads to to the Unity dial by name handler. 3 leads to the Unity sign-in handler).
    With type-ahead (a natural feature of the VXML standard) regular users will type 1-3 to check their voice mail.
    I'd like to hear from other CVP designers. It's not that they can't be coded.
    Regards,
    Geoff

  • External callers cannot hear greetings

    Dears,
    i have setup a unity connection for all the users, PSTN  callers cannot hear user default greetings of the user voice mail , i have enabled RTP from unity connection server to voice gateway which are in different subnet but  CUCM and UN are in 1 subnet.
    Any hints where things are going wrong
    Thanks

    Dears
    Anyone else can put some shade on the query above. The calls gets transferred to the unity connection I can see the call duration keeps on increasing on the mobile phone, but I cannot hear the unity connection user greeting nor whatever I speak it drops as an voice mail to the user mailbox.
    thanks

  • Unity - Greeting Player in Browser -- Java Issue

    Guys,
    I have Unity conneciton 9.x,   The embed Java greeting player is not working..
    I suspect one of these reason :
    Java version ( too rescent )
    Too much security on Java
    Browser version issue
    ... I have try many thing,  lower security, try 3 different browser, but nothing.. .I can't see the player.
    Anyone can suggest me something ?
    thanks

    Is there any error message? Or the Media Master is not seen at all? And complete Unity Connection version? Output of 'show version active'.
    There are a few defects with Java 7 and CUC 9,
    CSCum81926 - Media Master not working properly on Internet Explorer with java 7 
    CSCug57088 - Cisco PCA Greetings Page Java Errors with JRE 7
    CSCuo44795 - Media Master Java Error: Missing Required Permission manifest attribute
    CSCug94328 - Not able to save recording in CPCA recorded via computer over Java 7 
    CSCuo66204 - UC: Media Master issue 
    CSCtw45908 - Trap call not woking on build CUC: 9.0.0.67 
    CSCuo94694 - Media Master jar signing Certificate expiry issue 
    CSCue74920 -  Media Master Playback& Recording and Help not working with win 7/java 7 
    Also try this,
    Go to Control Panel > Java > Advanced Tab > Disable Verification
    There is a patch released by the developers for most of the defects. Either upgrade the server to a fixed version or open a TAC case to get the patch. The patch may not solve your issue and this could be a new issue as well. Happens all the time when Java releases new versions.
    HTH
    Anirudh

  • Unity Connections remote call sign-in issue.

    I have some users that when they dial there DID from outside they hit there VM press star and are prompted for their sign-in number and pin. Then I have some users that do the same thing, but the greeting just continues to play. I am sure there is a simple fix to this, but I cannot seem to find it. Hoping someone out here can lead me in the correct direction.
    I am running Unity Connection 8.6.2.
    Thanks in advance,
    Dave

    Hi Dave,
    I would check the following on a "working" vs "non-working" user;
    User> Edit> Caller Input> * (star)> send to Sign-in
    Cheers!
    Rob
    Please support CSC helps Kiva
    https://supportforums.cisco.com/blog/12122171/cisco-support-community-helps-kiva

  • Want to understand the Difference between Attempt sign in and sign in in Unity Connection

    I would like to understand the difference between Attempt sign in and sign in in Unity Connection.
    If I do a direct routing rule to attempt sign in and another routing rule directly to sign in, what would be the difference for the caller (inside caller with or without voicemail and also outside caller with or without voicemail)?  Thank you!  Lise

    Attempt Sign-In—Sends the call to the user sign in conversation, if the calling number belongs to a user. The calling number is used as the ID. If the call is not from a user, the next rule in the routing table is applied to the call information.
    Sign-In—Sends the call to the user sign in conversation, which prompts the caller to enter an ID.

  • Help with lightdb-unity-greeter dependencies(lib3, light-themes)

    Hello all, I've spent 3 days of my spring break fresh installing Arch Linux on a laptop I bought as my 2nd distro (I had ubuntu for a week). I've been able to sort through all the problems I've ran into so far with the wiki and forum posts but I'm having trouble installing the dependencies so I can makepkg the pkgbuild in the unity-greeter folder I have.
    The 2 dependencies I have missing are:
    ==> Making package: lightdm-unity-greeter 13.10.2-100 (Tue Mar 25 23:47:56 UTC 2014)
    ==> Checking runtime dependencies...
    ==> Installing missing dependencies...
    error: target not found: libindicator3
    error: target not found: light-themes
    ==> ERROR: 'pacman' failed to install missing dependencies.
    Google searching brings me to the AUR for lightdm-unity-greeter https://aur.archlinux.org/packages/ligh … setlang=nl
    which suggests I use the PKGBUILD's under chenxiaolong github to solve the error (https://github.com/chenxiaolong/Unity-for-Arch)
    https://github.com/chenxiaolong/Unity-f … r/PKGBUILD
    For the libindicator pkgbuild when I makepkg it gives me:
    configure: error: Package requirements (gtk+-3.0 >= 3.6
    gmodule-2.0
    gio-unix-2.0 >= 2.37
    libido3-0.1 >= 13.10.0) were not met:
    Requested 'libido3-0.1 >= 13.10.0' but version of libido is 12.10.2
    Consider adjusting the PKG_CONFIG_PATH environment variable if you
    installed software in a non-standard prefix.
    Alternatively, you may set the environment variables LIBINDICATOR_CFLAGS
    and LIBINDICATOR_LIBS to avoid the need to call pkg-config.
    See the pkg-config man page for more details.
    ==> ERROR: A failure occurred in build().
    Aborting...
    and for the updated ido pkgbuild (on the AUR page it's chen fix for the lib3 dependency)
    (https://github.com/chenxiaolong/Unity-f … o/PKGBUILD)
    I get
    checking for LIBINDICATOR... no
    configure: error: Package requirements (gtk+-3.0 >= 3.6
    gmodule-2.0
    gio-unix-2.0 >= 2.37
    libido3-0.1 >= 13.10.0) were not met:
    Requested 'libido3-0.1 >= 13.10.0' but version of libido is 12.10.2
    Consider adjusting the PKG_CONFIG_PATH environment variable if you
    installed software in a non-standard prefix.
    Alternatively, you may set the environment variables LIBINDICATOR_CFLAGS
    and LIBINDICATOR_LIBS to avoid the need to call pkg-config.
    See the pkg-config man page for more details.
    ==> ERROR: A failure occurred in build().
    Aborting...
    My DE is xfce if it matters at all.
    I can't find anything else searching for this, can someone point me in the right direction?
    Last edited by Graxin (2014-03-26 07:23:17)

    Any one found a solution to this?

  • [SOLVED] Cannot change the lightdm-unity-greeter background

    Hi.
    So I installed the lightdm-ubuntu and lightdm-unity-greeter (which needed lightdm-ubuntu) from the AUR, and when I read both the wiki and the web, they said that I needed to install the lightdm package, not lightdm-ubuntu (when I install lightdm-ubuntu, it conflicts with lightdm, forcing me to remove it). So I installed it, used it, saw the nice login screen, but I would like to remove the dots showing up over the background AND change the background. I read that there is a config in the /etc/lightdm folder, but when I tried finding it, it was not there.
    ls /etc/lightdm showed me:
    keys.conf lightdm-gtk-greeter.conf users.conf
    lightdm.conf lightdm-gtk-greeter.conf~
    lightdm.conf.pacsave lightdm-gtk-greeter.conf.pacsave
    I do not want to have the background of the login the same as my background when I'm logged in, so I don't think gnome-settings-daemon-ubuntu and accountsservice-ubuntu should be needed. And even if they are, I would like to find a way to change it without installing those packages, since I can't install them easily -- this computer is a school computer and is connected through a filter, which unnecessarily blocks many sites (like say, eclipse.org and gnu.org, but that is not the point), and freedesktop.org is one of them.
    I would appreciate if anyone knows how to do that.
    Thanks.
    EDIT: Solved. faidoc's answer was priceless.
    Last edited by Technicolor (2012-10-04 13:54:05)

    hi everybody from the Indian Ocean , especially Rodrigues Island-Republic of Mauritius !
    I am now running a Archlinux Vm with 3 desktop environemnts such as Gnome, Mate and Xfce4 . I am encounting a conflict file issue between lightdm , lightdm-Ubuntu and lightdm-gtk-greeter.conf !
    The system says that lightdm-gtk-greeter.conf creates a conflict and , when installing Unity as per " chenxiaolong :https://github.com/chenxiaolong/Unity-for-Arch" or through the Wiki method I am always stuck ! I don't even have the " /usr/share/glib-2.0/schemas/com.canonical.unity-greeter.gschema.xml" ! The nearest I've got is " com.canonical.unity-gtk-module.gschema " ! This means that even lightdm-ubuntu-greeter cannot be installed ......What must I do ?

  • Import wav file in Unity 7 for subscriber greeting?

    We are updating info on the voicemail for our general mailboxes on all of our sites. The recording I have to make is long and basically the same for all the sites. Is there any way to import a greeting or copy and paste a wav file in to Unity so I can use one recording and don't have to record a minute long recording 16 times that I will screw up 100 times?

    Ahh...  You wrote 'unity' and my brain added the 'connection'.  Sorry about that.  From memory, it's a really similar process though.  I did leave out a step though.  In unity connection, after going to the greetings section you have to select the greeting you want to update/review (standard, alternate, etc).  Then scroll down for the "play/record" button.  I don't have a unity server to check but am hoping thatwill be close enough to get you there.

  • Configure Sign-In Unity 7.0(2)

    I am looking for a way to configure the Sign-In function.  I am having an issue where people are being directed there and if they don't respond properly (or at all) the calls are being forwarded to an unattended mailbox.  My question is where do I go to conifgure the Sign-In function so that I can stop this behavior?

    Hi Josh,
    Depending on how the calls are coming into UC (forwarded, or direct) you'll want to take a look at the Call Routing rules and see where the calls are being sent.  If you're unable to determine where the call is being routed to, use either RTMT or download the remote port monitor tool from ciscounitytools.com (there is a couple configuration settings you need to perform in the help file for the tool to work) and you can see what call handler/greeting is being played and then go to that object and configure the after greeting actions for it.
    Hope that helps,
    Brad

  • Error when building lightdm-unity-greeter

    Hi,
    I built Unity from git last night, and today I've failed to make lightdm-unity-greeter with this error:
    make[2]: Entering directory `/home/isolet/Unity-for-Arch-Extra/lightdm-unity-greeter/src/unity-greeter-13.10.2/src'
    VALAC unity_greeter_vala.stamp
    fixes.vapi:4.5-4.33: error: `Posix' already contains a definition for `MCL_CURRENT'
    public const int MCL_CURRENT;
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    posix.vapi:2308.2-2308.30: note: previous definition of `MCL_CURRENT' was here
    public const int MCL_CURRENT;
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    fixes.vapi:6.5-6.32: error: `Posix' already contains a definition for `MCL_FUTURE'
    public const int MCL_FUTURE;
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    posix.vapi:2310.2-2310.29: note: previous definition of `MCL_FUTURE' was here
    public const int MCL_FUTURE;
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    fixes.vapi:8.5-8.23: error: `Posix' already contains a definition for `mlockall'
    public int mlockall (int flags);
    ^^^^^^^^^^^^^^^^^^^
    posix.vapi:2312.2-2312.20: note: previous definition of `mlockall' was here
    public int mlockall (int flags);
    ^^^^^^^^^^^^^^^^^^^
    fixes.vapi:10.5-10.25: error: `Posix' already contains a definition for `munlockall'
    public int munlockall ();
    ^^^^^^^^^^^^^^^^^^^^^
    posix.vapi:2314.2-2314.22: note: previous definition of `munlockall' was here
    public int munlockall ();
    ^^^^^^^^^^^^^^^^^^^^^
    Compilation failed: 4 error(s), 0 warning(s)
    make[2]: *** [unity_greeter_vala.stamp] Error 1
    make[2]: Leaving directory `/home/isolet/Unity-for-Arch-Extra/lightdm-unity-greeter/src/unity-greeter-13.10.2/src'
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory `/home/isolet/Unity-for-Arch-Extra/lightdm-unity-greeter/src/unity-greeter-13.10.2'
    make: *** [all] Error 2
    The configure log seems nothing goes wrong:
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for style of include used by make... GNU
    checking for gcc... gcc
    checking whether the C compiler works... yes
    checking for C compiler default output file name... a.out
    checking for suffix of executables...
    checking whether we are cross compiling... no
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking whether gcc understands -c and -o together... yes
    checking dependency style of gcc... gcc3
    checking for valac... /usr/bin/valac
    checking whether /usr/bin/valac is at least version 0.20.0... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking whether make supports nested variables... (cached) yes
    checking for pkg-config... /usr/bin/pkg-config
    checking pkg-config is at least version 0.16... yes
    checking for UNITY_GREETER... yes
    checking whether NLS is requested... yes
    checking for intltool >= 0.35.0... 0.50.2 found
    checking for intltool-update... /usr/bin/intltool-update
    checking for intltool-merge... /usr/bin/intltool-merge
    checking for intltool-extract... /usr/bin/intltool-extract
    checking for xgettext... /usr/bin/xgettext
    checking for msgmerge... /usr/bin/msgmerge
    checking for msgfmt... /usr/bin/msgfmt
    checking for gmsgfmt... /usr/bin/msgfmt
    checking for perl... /usr/bin/perl
    checking for perl >= 5.8.1... 5.18.1
    checking for XML::Parser... ok
    checking that generated files are newer than configure... done
    configure: creating ./config.status
    config.status: creating Makefile
    config.status: creating data/Makefile
    config.status: creating po/Makefile.in
    config.status: creating src/Makefile
    config.status: creating tests/Makefile
    config.status: creating config.h
    config.status: config.h is unchanged
    config.status: executing depfiles commands
    config.status: executing po/stamp-it commands
    Since I'm new to Arch and not that familiar with C/C++ compiling, can somebody help take a look at this and give me some ideas ?
    Your help will be greatly appreciated!
    Last edited by isolet (2013-10-16 03:09:02)

    hi everybody from the Indian Ocean , especially Rodrigues Island-Republic of Mauritius !
    I am now running a Archlinux Vm with 3 desktop environemnts such as Gnome, Mate and Xfce4 . I am encounting a conflict file issue between lightdm , lightdm-Ubuntu and lightdm-gtk-greeter.conf !
    The system says that lightdm-gtk-greeter.conf creates a conflict and , when installing Unity as per " chenxiaolong :https://github.com/chenxiaolong/Unity-for-Arch" or through the Wiki method I am always stuck ! I don't even have the " /usr/share/glib-2.0/schemas/com.canonical.unity-greeter.gschema.xml" ! The nearest I've got is " com.canonical.unity-gtk-module.gschema " ! This means that even lightdm-ubuntu-greeter cannot be installed ......What must I do ?

  • Lightdm with unity-greeter won't load

    I've been attempting to install lightdm and the unity greeter, and I'm a bit stuck here.
    I've installed the lightdm-ubuntu and lightdm-unity-greeter packages from the AUR.  It starts up normally, but there is no gear available to choose session type, and logging in causes the DM to just restart and go back to the logon page.
    I was able to use lightdm and lightdm-gtk-greeter successfully.  Also, running startx from another tty successfully starts my session (in my case, xmonad).  I've attached my configuration files and log files, in case anyone can make heads or tails of them.
    File dump follows!
    Here's my etc/lightdm/lightdm.conf:
    # General configuration
    # start-default-seat = True to always start one seat if none are defined in the configuration
    # greeter-user = User to run greeter as
    # minimum-display-number = Minimum display number to use for X servers
    # minimum-vt = First VT to run displays on
    # lock-memory = True to prevent memory from being paged to disk
    # user-authority-in-system-dir = True if session authority should be in the system location
    # guest-account-script = Script to be run to setup guest account
    # log-directory = Directory to log information to
    # run-directory = Directory to put running state in
    # cache-directory = Directory to cache to
    # xsessions-directory = Directory to find X sessions
    # remote-sessions-directory = Directory to find remote sessions
    # xgreeters-directory = Directory to find X greeters
    [LightDM]
    #start-default-seat=true
    #greeter-user=lightdm
    #minimum-display-number=0
    #minimum-vt=7
    #lock-memory=true
    #user-authority-in-system-dir=false
    #guest-account-script=guest-account
    #log-directory=/var/log/lightdm
    #run-directory=/var/run/lightdm
    #cache-directory=/var/cache/lightdm
    xsessions-directory=/usr/share/xsessions
    #remote-sessions-directory=/usr/share/lightdm/remote-sessions
    #xgreeters-directory=/usr/share/xgreeters
    # Seat defaults
    # type = Seat type (xlocal, xremote)
    # xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
    # xserver-layout = Layout to pass to X server
    # xserver-config = Config file to pass to X server
    # xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
    # xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
    # xdmcp-port = XDMCP UDP/IP port to communicate on
    # xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
    # greeter-session = Session to load for greeter
    # greeter-hide-users = True to hide the user list
    # greeter-allow-guest = True if the greeter should show a guest login option
    # greeter-show-manual-login = True if the greeter should offer a manual login option
    # greeter-show-remote-login = True if the greeter should offer a remote login option
    # user-session = Session to load for users
    # allow-guest = True if guest login is allowed
    # guest-session = Session to load for guests (overrides user-session)
    # session-wrapper = Wrapper script to run session with
    # display-setup-script = Script to run when starting a greeter session (runs as root)
    # greeter-setup-script = Script to run when starting a greeter (runs as root)
    # session-setup-script = Script to run when starting a user session (runs as root)
    # session-cleanup-script = Script to run when quitting a user session (runs as root)
    # autologin-guest = True to log in as guest by default
    # autologin-user = User to log in with by default (overrides autologin-guest)
    # autologin-user-timeout = Number of seconds to wait before loading default user
    # autologin-session = Session to load for automatic login (overrides user-session)
    # exit-on-failure = True if the daemon should exit if this seat fails
    [SeatDefaults]
    type=xlocal
    xserver-command=X
    #xserver-layout=
    #xserver-config=
    #xserver-allow-tcp=false
    #xdmcp-manager=
    #xdmcp-port=177
    #xdmcp-key=
    #greeter-session=lightdm-unity-greeter
    #greeter-hide-users=false
    #greeter-allow-guest=true
    #greeter-show-manual-login=false
    #greeter-show-remote-login=true
    user-session=XMonad
    #allow-guest=true
    #guest-session=UNIMPLEMENTED
    #session-wrapper=lightdm-session
    #display-setup-script=
    #greeter-setup-script=
    #session-setup-script=
    #session-cleanup-script=
    #autologin-guest=false
    #autologin-user=
    #autologin-user-timeout=0
    #autologin-session=UNIMPLEMENTED
    #exit-on-failure=false
    # Seat configuration
    # Each seat must start with "Seat:".
    # Uses settings from [SeatDefaults], any of these can be overriden by setting them in this section.
    #[Seat:0]
    # XDMCP Server configuration
    # enabled = True if XDMCP connections should be allowed
    # port = UDP/IP port to listen for connections on
    # key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
    # The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn. Alternatively
    # it can be a word and the first 7 characters are used as the key.
    greeter-session=unity-greeter
    [XDMCPServer]
    #enabled=false
    #port=177
    #key=
    # VNC Server configuration
    # enabled = True if VNC connections should be allowed
    # port = TCP/IP port to listen for connections on
    [VNCServer]
    #enabled=false
    #port=5900
    #width=1024
    #height=768
    #depth=8
    My contents of /usr/share/xsessions:
    $ ls /usr/share/xsessions
    xmonad.desktop
    /usr/share/xsessions/xmonad.desktop
    [Desktop Entry]
    Encoding=UTF-8
    Name=XMonad
    Comment=Lightweight tiling window manager
    Exec=xmonad
    Icon=xmonad.png
    Type=XSession
    And the log files, after boot and one log on attempt:
    /var/log/lightdm/lightdm.log
    [+0.03s] DEBUG: Logging to /var/log/lightdm/lightdm.log
    [+0.03s] DEBUG: Starting Light Display Manager 1.4.0, UID=0 PID=355
    [+0.03s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
    [+0.03s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
    [+0.27s] DEBUG: Registered seat module xlocal
    [+0.27s] DEBUG: Registered seat module xremote
    [+0.27s] DEBUG: Adding default seat
    [+0.27s] DEBUG: Starting seat
    [+0.27s] DEBUG: Starting new display for greeter
    [+0.27s] DEBUG: Starting local X display
    [+0.31s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
    [+0.31s] DEBUG: Using VT 7
    [+0.31s] DEBUG: Activating VT 7
    [+0.36s] DEBUG: Logging to /var/log/lightdm/x-0.log
    [+0.43s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0
    [+0.43s] DEBUG: Launching X Server
    [+0.43s] DEBUG: Launching process 368: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
    [+0.44s] DEBUG: Waiting for ready signal from X server :0
    [+0.44s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
    [+0.44s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
    [+2.46s] DEBUG: Got signal 10 from process 368
    [+2.46s] DEBUG: Got signal from X server :0
    [+2.46s] DEBUG: Connecting to XServer :0
    [+2.51s] DEBUG: Starting greeter
    [+2.51s] DEBUG: Started session 387 with service 'lightdm-greeter', username 'lightdm'
    [+3.33s] DEBUG: Session 387 authentication complete with return value 0: Success
    [+3.33s] DEBUG: Greeter authorized
    [+3.33s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
    [+3.38s] DEBUG: Session 387 running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter
    [+4.53s] DEBUG: Greeter connected version=1.4.0
    [+4.53s] DEBUG: Greeter connected, display is ready
    [+4.53s] DEBUG: New display ready, switching to it
    [+4.53s] DEBUG: Activating VT 7
    [+5.34s] DEBUG: Greeter start authentication for jabenze
    [+5.34s] DEBUG: Started session 424 with service 'lightdm', username 'jabenze'
    [+5.36s] DEBUG: Greeter start authentication for jabenze
    [+5.36s] DEBUG: Session 424: Sending SIGTERM
    [+5.36s] DEBUG: Started session 426 with service 'lightdm', username 'jabenze'
    [+5.36s] DEBUG: Session 424 terminated with signal 15
    [+5.36s] DEBUG: Session 424 failed during authentication
    [+5.39s] DEBUG: Session 426 got 1 message(s) from PAM
    [+5.39s] DEBUG: Prompt greeter with 1 message(s)
    [+13.53s] DEBUG: Continue authentication
    [+13.55s] DEBUG: Session 426 authentication complete with return value 0: Success
    [+13.55s] DEBUG: Authenticate result for user jabenze: Success
    [+13.56s] DEBUG: User jabenze authorized
    [+13.56s] DEBUG: Greeter requests session ubuntu
    [+13.56s] DEBUG: Using session ubuntu
    [+13.56s] DEBUG: Stopping greeter
    [+13.56s] DEBUG: Session 387: Sending SIGTERM
    [+13.59s] DEBUG: Greeter closed communication channel
    [+13.59s] DEBUG: Session 387 exited with return value 0
    [+13.59s] DEBUG: Greeter quit
    [+13.60s] DEBUG: Dropping privileges to uid 1000
    [+13.60s] DEBUG: Calling setresgid
    [+13.60s] DEBUG: Calling setresuid
    [+13.62s] DEBUG: Restoring privileges
    [+13.62s] DEBUG: Calling setresuid
    [+13.62s] DEBUG: Calling setresgid
    [+13.63s] DEBUG: Dropping privileges to uid 1000
    [+13.63s] DEBUG: Calling setresgid
    [+13.63s] DEBUG: Calling setresuid
    [+13.63s] DEBUG: Writing /home/jabenze/.dmrc
    [+13.70s] DEBUG: Restoring privileges
    [+13.70s] DEBUG: Calling setresuid
    [+13.70s] DEBUG: Calling setresgid
    [+13.73s] DEBUG: Failed to load session file /usr/share/xsessions/ubuntu.desktop: No such file or directory
    [+13.73s] DEBUG: Failed to start greeter
    [+13.73s] DEBUG: Stopping display
    [+13.73s] DEBUG: Session 426: Sending SIGTERM
    [+13.73s] DEBUG: Session 426 terminated with signal 15
    [+13.73s] DEBUG: User session quit
    [+13.73s] DEBUG: Sending signal 15 to process 368
    [+14.28s] DEBUG: Process 368 exited with return value 0
    [+14.28s] DEBUG: X server stopped
    [+14.28s] DEBUG: Removing X server authority /var/run/lightdm/root/:0
    [+14.28s] DEBUG: Releasing VT 7
    [+14.28s] DEBUG: Display server stopped
    [+14.28s] DEBUG: Display stopped
    [+14.28s] DEBUG: Active display stopped, switching to greeter
    [+14.28s] DEBUG: Switching to greeter
    [+14.28s] DEBUG: Starting new display for greeter
    [+14.28s] DEBUG: Starting local X display
    [+14.28s] DEBUG: Using VT 7
    [+14.28s] DEBUG: Logging to /var/log/lightdm/x-0.log
    [+14.28s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0
    [+14.28s] DEBUG: Launching X Server
    [+14.28s] DEBUG: Launching process 463: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
    [+14.28s] DEBUG: Waiting for ready signal from X server :0
    [+14.88s] DEBUG: Got signal 10 from process 463
    [+14.88s] DEBUG: Got signal from X server :0
    [+14.88s] DEBUG: Connecting to XServer :0
    [+14.88s] DEBUG: Starting greeter
    [+14.88s] DEBUG: Started session 468 with service 'lightdm-greeter', username 'lightdm'
    [+14.90s] DEBUG: Session 468 authentication complete with return value 0: Success
    [+14.90s] DEBUG: Greeter authorized
    [+14.90s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
    [+14.90s] DEBUG: Session 468 running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter
    [+15.01s] DEBUG: Greeter connected version=1.4.0
    [+15.01s] DEBUG: Greeter connected, display is ready
    [+15.01s] DEBUG: New display ready, switching to it
    [+15.01s] DEBUG: Activating VT 7
    [+15.01s] DEBUG: Stopping greeter display being switched from
    [+15.10s] DEBUG: Greeter start authentication for jabenze
    [+15.10s] DEBUG: Started session 500 with service 'lightdm', username 'jabenze'
    [+15.11s] DEBUG: Session 500 got 1 message(s) from PAM
    [+15.11s] DEBUG: Prompt greeter with 1 message(s)
    [+15.15s] DEBUG: Greeter start authentication for jabenze
    [+15.15s] DEBUG: Session 500: Sending SIGTERM
    [+15.15s] DEBUG: Started session 502 with service 'lightdm', username 'jabenze'
    [+15.15s] DEBUG: Session 500 terminated with signal 15
    [+15.15s] DEBUG: Session 500 failed during authentication
    [+15.15s] DEBUG: Session 502 got 1 message(s) from PAM
    [+15.15s] DEBUG: Prompt greeter with 1 message(s)
    /var/log/lightdm/x-0-greeter.log:
    ** (process:468): WARNING **: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
    Activating service name='org.a11y.atspi.Registry'
    [+0.00s] DEBUG: unity-greeter.vala:438: Starting unity-greeter 12.10.4 UID=999 LANG=(null)
    [+0.00s] DEBUG: unity-greeter.vala:441: Setting cursor
    Successfully activated service 'org.a11y.atspi.Registry'
    [+0.00s] DEBUG: unity-greeter.vala:455: Loading command line options
    [+0.00s] DEBUG: unity-greeter.vala:483: Setting GTK+ settings
    ** (at-spi2-registryd:490): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
    ** (at-spi2-registryd:490): WARNING **: Unable to register client with session manager
    [+0.04s] DEBUG: unity-greeter.vala:506: Creating Unity Greeter
    [+0.04s] DEBUG: unity-greeter.vala:55: Creating background surface
    [+0.04s] DEBUG: Connecting to display manager...
    [+0.04s] DEBUG: Wrote 17 bytes to daemon
    [+0.04s] DEBUG: Read 8 bytes from daemon
    [+0.04s] DEBUG: Read 149 bytes from daemon
    [+0.04s] DEBUG: Connected version=1.4.0 default-session=XMonad show-manual-login=false hide-users=false has-guest-account=true show-remote-login=true
    [+0.06s] DEBUG: menubar.vala:342: LANG=(null) LANGUAGE=(null)
    [+0.06s] WARNING: File '/usr/lib/indicators3/7/libsession.so' does not exist.
    [+0.06s] WARNING: File '/usr/lib/indicators3/7/libdatetime.so' does not exist.
    [+0.06s] WARNING: File '/usr/lib/indicators3/7/libpower.so' does not exist.
    [+0.06s] WARNING: File '/usr/lib/indicators3/7/libsoundmenu.so' does not exist.
    [+0.06s] WARNING: File '/usr/lib/indicators3/7/libapplication.so' does not exist.
    [+0.06s] DEBUG: menubar.vala:360: LANG=(null) LANGUAGE=(null)
    [+0.07s] DEBUG: Loading users from org.freedesktop.Accounts
    [+0.07s] DEBUG: Loading user /org/freedesktop/Accounts/User1000
    [+0.08s] DEBUG: Loading sessions from org.freedesktop.DisplayManager
    [+0.08s] DEBUG: user-list.vala:950: Adding/updating user jabenze ()
    [+0.08s] WARNING: Could not get accounts property XKeyboardLayouts
    [+0.08s] WARNING: Could not get accounts property XHasMessages
    [+0.08s] CRITICAL: g_variant_get_type: assertion `value != NULL' failed
    [+0.08s] CRITICAL: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
    [+0.08s] CRITICAL: g_variant_get_type_string: assertion `value != NULL' failed
    [+0.08s] WARNING: Unexpected accounts property type for XHasMessages: (null)
    [+0.08s] CRITICAL: g_variant_unref: assertion `value != NULL' failed
    [+0.08s] WARNING: Could not get accounts property XKeyboardLayouts
    [+0.08s] WARNING: Could not get accounts property XHasMessages
    [+0.08s] CRITICAL: g_variant_get_type: assertion `value != NULL' failed
    [+0.08s] CRITICAL: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
    [+0.08s] CRITICAL: g_variant_get_type_string: assertion `value != NULL' failed
    [+0.08s] WARNING: Unexpected accounts property type for XHasMessages: (null)
    [+0.08s] CRITICAL: g_variant_unref: assertion `value != NULL' failed
    [+0.08s] WARNING: Could not get accounts property XKeyboardLayouts
    [+0.08s] WARNING: Could not get accounts property XHasMessages
    [+0.08s] CRITICAL: g_variant_get_type: assertion `value != NULL' failed
    [+0.08s] CRITICAL: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
    [+0.08s] CRITICAL: g_variant_get_type_string: assertion `value != NULL' failed
    [+0.08s] WARNING: Unexpected accounts property type for XHasMessages: (null)
    [+0.08s] CRITICAL: g_variant_unref: assertion `value != NULL' failed
    [+0.08s] DEBUG: user-list.vala:932: Adding guest account entry
    [+0.13s] DEBUG: Loaded session /usr/share/xsessions/xmonad.desktop (XMonad, Lightweight tiling window manager)
    [+0.13s] WARNING: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory
    [+0.13s] DEBUG: Starting authentication for user jabenze...
    [+0.13s] DEBUG: Wrote 23 bytes to daemon
    [+0.18s] DEBUG: Starting authentication for user jabenze...
    [+0.18s] DEBUG: Wrote 23 bytes to daemon
    [+0.18s] DEBUG: main-window.vala:176: Screen is 3840x1080 pixels
    [+0.18s] DEBUG: main-window.vala:182: Monitor 0 is 1920x1080 pixels at 0,0
    [+0.18s] DEBUG: main-window.vala:182: Monitor 1 is 1920x1080 pixels at 1920,0
    [+0.18s] DEBUG: unity-greeter.vala:509: Showing greeter
    [+0.18s] DEBUG: unity-greeter.vala:198: Showing main window
    [+0.21s] DEBUG: background.vala:470: Regenerating backgrounds
    [+0.21s] DEBUG: background.vala:68: Making background /usr/share/backgrounds/warty-final-ubuntu.png at 1920x1080
    [+0.21s] WARNING: unity-greeter.vala:523: Error starting nm-applet: Failed to execute child process "nm-applet" (No such file or directory)
    [+0.21s] DEBUG: unity-greeter.vala:527: Starting main loop
    [+0.21s] DEBUG: Read 8 bytes from daemon
    [+0.21s] DEBUG: Read 37 bytes from daemon
    [+0.21s] DEBUG: Ignoring prompt authentication with invalid sequence number 1
    [+0.21s] DEBUG: settings-daemon.vala:97: Could not start gnome-settings-daemon over DBus: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files
    [+0.27s] DEBUG: Setting keyboard layout to 'us'
    [+0.29s] DEBUG: Read 8 bytes from daemon
    [+0.29s] DEBUG: Read 37 bytes from daemon
    [+0.29s] DEBUG: Prompt user with 1 message(s)
    [+0.32s] DEBUG: unity-greeter.vala:181: starting system-ready sound
    [+0.38s] DEBUG: background.vala:117: Render of background /usr/share/backgrounds/warty-final-ubuntu.png complete
    /var/log/lightdm/x-0.log
    X.Org X Server 1.13.1
    Release Date: 2012-12-13
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.7.0-1-ARCH x86_64
    Current Operating System: Linux frankie 3.6.10-1-ARCH #1 SMP PREEMPT Tue Dec 11 09:40:17 CET 2012 x86_64
    Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=51606072-17ca-431e-a2bf-ba739d1cfeb1 ro quiet
    Build Date: 16 December 2012 04:45:14PM
    Current version of pixman: 0.28.2
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 26 13:36:33 2012
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    Loading extension NV-GLX
    Loading extension NV-CONTROL
    Loading extension XINERAMA

    I am also stuck on this. I get pretty much the exact same result. Until I figure it out I'll be doing the quick startx.

  • BULK Greeting Change in Unity Connection 8.6 and higher

    In Cisco Unity Connection can you have the same voicemail greeting on 330 different voice mail boxes?  These are for stores  and if the store main number is busy or not answered it will got to voicemail
    Each of the voicemail box then emails the voicemail as attachment to voicemail box owner?

    Hi Anirudh,
    I am not clear on what you mean by this sentence:
    Each extension in the 330 sites will be unique and the same extension can be used for the user on Unity  - a total of 330 users on Unity.
    The Callflow we need looks like this.
    Call from PSTN to SITEA---> CFAtoVM --> Plays Standard Greeting ---MWI for PhoneA at SITEA Turns on
    Call from PSTN to SITEB---> CFAtoVM --> Plays Standard Greeting ---MWI for PhoneB at SITEB Turns on
    regards
    Andrew

Maybe you are looking for