[cisco-voip] Jabber and Finesse

Thu Mar 19 08:58:37 EDT 2020

It has not had to be the second line for CCX in my experience, seems to  work just fine.

From: Terry Oakley <Terry.Oakley at rdc.ab.ca>
Sent: Thursday, March 19, 2020 12:19 AM
To: NateCCIE <nateccie at gmail.com>
Cc: Jose Colon II <jcolon424 at gmail.com>; Pawlowski, Adam <ajp26 at buffalo.edu>; Terry Oakley via cisco-voip <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Jabber and Finesse

I have the agent on the second line.   Will check that in the morning,  thank you
And will check to see if version of expressway is the issue,

Terry

Sent from my BlackBerry — the most secure mobile device — via the TELUS Network
From: nateccie at gmail.com<mailto:nateccie at gmail.com>
Sent: March 18, 2020 10:05 PM
To: Terry.Oakley at rdc.ab.ca<mailto:Terry.Oakley at rdc.ab.ca>
Cc: jcolon424 at gmail.com<mailto:jcolon424 at gmail.com>; ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Jabber and Finesse

CAUTION: This email is from an external source. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Is the UCCX the primary line or the 2nd line on the jabber?  You need newer expressway CUCM and jabber to support jabber multi line.

I don’t know about UCCX, but i am told with CCE, the agent line has to be the primary line on jabber.
Sent from my iPhone

On Mar 18, 2020, at 8:25 PM, Terry Oakley via cisco-voip <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>> wrote:

Thank you for the quick replies.   I know all of you are undergoing immense pressure so I truly appreciate the assistance.   I have triple checked that the UCCX extension is just on the Jabber Windows client.  When I try and dial the extension I get the nice Cisco lady telling me the number cannot be completed as dialed.   If I dial the primary extension on the Jabber client it works.    If I put the UCCX extension on a physical set (8851) it will ring.

When I am on the Jabber Windows client I have checked the CSS for the UCCX extension it is fine, same as the primary line.  Double checked to make sure the extension was an active number.     Allow Control of Device from CTI is enabled.   There must be some little check box or something that I have missed but I have stared at the page so long it all looks the same.

Thanks again

Terry

________________________________
From: Jose Colon II <jcolon424 at gmail.com<mailto:jcolon424 at gmail.com>>
Sent: Wednesday, March 18, 2020 4:38:26 PM
To: Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>
Cc: Terry Oakley <Terry.Oakley at rdc.ab.ca<mailto:Terry.Oakley at rdc.ab.ca>>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Jabber and Finesse

CAUTION: This email is from an external source. Do not click links or open attachments unless you recognize the sender and know the content is safe.

I think that is the key to the issue. UCCX extension can only be registered to one device.

On Wed, Mar 18, 2020 at 5:37 PM Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>> wrote:

Hi Terry,

I had the same problem when I had my CCX extension on multiple items, even when unregistered. Clicking on ready resulted in an error, but the first time I made a call with it by opening the keypad it started working and I could go ready. Since the CCX extension is just an extension, you should be able to dial it regardless of what Finesse is doing, assuming it is in a partition that you can dial but it may not be.

After I made sure the extension was on nothing but my Jabber client, and I had signed out and back in, it began to work fine.

I haven’t heard any comments from anyone else and we moved ~75 seats to Jabber MRA and Finesse remote this week.

Adam

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Terry Oakley via cisco-voip
Sent: Wednesday, March 18, 2020 6:29 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Jabber and Finesse

We have on prem CUCM running 12.5.1.   We also have IM and Presence and UCCX for our phone queues.   I am trying to figure out if I can move our phone queues to Jabber and connect to Finesse via remote access (through VM Ware).    I seem to be able to get part way but when I try to make a call to the queue the Finesse line will not answer and unless I go off hook first on the Jabber app I cannot go to Ready on the Finesse side .   I cannot even dial it just directly.   I can use that line and dial out from Jabber but for some reason I cannot get the line to be recognized on the Finesse side.   I am sure I probably missed something in my haste so if anyone of you have successfully done something like this I would appreciate a simple how to.

I hope all of you are safe and your families as well.

Terry

Terry Oakley

Telecommunications Coordinator | Information Technology Services

Red Deer College |100 College Blvd. | Box 5005 | Red Deer | Alberta | T4N 5H5

work (403) 342-3521   |  FAX (403) 343-4034

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7CTerry.Oakley%40rdc.ab.ca%7Ce68b61f310604d832a3408d7cbbab919%7C3aed1c227c31455eb67a279994fffbd6%7C1%7C0%7C637201875144948518&sdata=mGqmz2a7bT3GFyIjzfDEKyN53r6xxDzPXavb2midLjg%3D&reserved=0>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200319/a303eb13/attachment.htm>