[cisco-voip] CUCM 10.5 and Office 365

2017-07-05 Thread Terry Oakley 
We are currently working towards moving our MS office products to Office 365.   
We have currently a hybrid 2013 Exchange server that is routing emails etc to 
either our legacy system or the new Office 365 cloud.   The part I am working 
on is unified messaging and how to get the UM portion to function so that voice 
mail is handled and the message waiting indicator is on or off.Anyone had 
experience with this configuration?

CUCM 10.5
Exchange 2007 inhouse
Exchange 2013 hybrid
Office 365 hosted in the cloud
Expressway C
Expressway E

Thanks

Terry

Sent from Mail for Windows 10

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] SX20 and Expressway C/E setup

2017-07-05 Thread Terry Oakley 
I have successfully licensed and setup a SX20 on our CUCM 10.5 and have made 
calls to and from the SX20 to both internal numbers, external numbers and a 
Jabber video call.   The problem I am having is placing a video call to an 
outside SIP number.   Does anyone have a guide or document that shows how the 
SX20 should be setup, SIP or H323 etc.When I look at the logs in Expressway 
I can see the Jabber calls to and from the SX20, but if I try to use the SX20 
to call an off site video there is no record in the logs.I ran the H323 and 
SIP debug commands and watched the SX20 call stream but frankly I am not sure 
of what I should be looking for in those logs.

Thanks

Terry

Sent from Mail for Windows 10

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] UCCX issue - Finesse agents unable to login

2017-07-05 Thread ROZA, Ariel 
Looks like Finesse can´t contact Active Directory to log in the Agent and the 
connection Times out. The reason the Connection Manager gives is 
ADOutOfServiceMsg


De: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] En nombre de 
Tooze-Froggatt, Peter (ISS)
Enviado el: lunes, 03 de julio de 2017 07:43 a.m.
Para: cisco-voip@puck.nether.net
Asunto: [cisco-voip] UCCX issue - Finesse agents unable to les ogin

Hi all,

Running 11.5.1.1-61 (ES01-45)

Thought I would find out if anyone has come across the following issue:

We had an outage on our Service Desk whereby users were unable to login and 
calls couldn't be answered. Looking at the MIVR logs, calls were coming in and 
being held on a CTI port until an agent was made available. You can see agents 
('X' and 'Y') attempting to login, but shortly afterwards, the following 
exceptions are thrown:

13971851: Jun 28 08:56:59.266 BST 
%MIVR-ICD_CTI-6-WATCHDOG_INFO:Watchdogthread:: A specific description for a 
trace=Watchdog thread - socket ClientId: 
FinesseSocket[addr=127.0.0.1,port=50556,localport=12028] timed out or stuck so 
closed.  q size is :0 time before last sent msg is : 1498636615424 time after 
last sent msg 1498636615424current time is : 1498636619266timeout is : 
12stuck time is : 3842time diff is : 124866
13971852: Jun 28 08:56:59.267 BST %MIVR-ICD_CTI-3-CLIENT_SOCKET_CLOSED:Client 
connection closed: A specific description for a trace=ClientConnMgr before 
closing Socket:socket is Socket[addr=127.0.0.1,port=50556,localport=12028] for 
agentID:X
13971853: Jun 28 08:56:59.267 BST %MIVR-ICD_CTI-3-CLIENT_SOCKET_CLOSED:Client 
connection closed: A specific description for a trace=ClientConnMgr posted 
ADOutOfServiceMsg for agentID:X, agentDN: 93903
13971854: Jun 28 08:56:59.268 BST %MIVR-ICD_CTI-3-CLIENT_SOCKET_CLOSED:Client 
connection closed: A specific description for a trace=ClientConnMgr before 
closing Socket:socket is Socket[addr=127.0.0.1,port=50556,localport=12028] for 
agentID:Y
13971855: Jun 28 08:56:59.268 BST %MIVR-ICD_CTI-3-CLIENT_SOCKET_CLOSED:Client 
connection closed: A specific description for a trace=ClientConnMgr posted 
ADOutOfServiceMsg for agentID:Y, agentDN: 93825
13971856: Jun 28 08:56:59.268 BST %MIVR-SS_RM-7-UNK:Processing msg: 
ADOutOfServiceMsg (Rsrc:X)
13971857: Jun 28 08:56:59.269 BST 
%MIVR-ICD_CTI-3-SOCKET_READ_EXCEPTION:Exception while reading from a socket 
input.: A description for the nature of the exception=ClientConnMgr: 
SocketException reading msg from input stream of socket : 
Socket[addr=127.0.0.1,port=50556,localport=12028] in client thread 
MIVR_ICD_CTI_client_thread_8775-19121-,Exception=java.net.SocketException: 
Socket closed
13971858: Jun 28 08:56:59.269 BST 
%MIVR-ICD_CTI-3-EXCEPTION:java.net.SocketException: Socket closed
13971859: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
java.net.SocketInputStream.socketRead0(Native Method)
13971860: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
java.net.SocketInputStream.read(SocketInputStream.java:152)
13971861: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
java.net.SocketInputStream.read(SocketInputStream.java:122)
13971862: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
java.io.DataInputStream.readFully(DataInputStream.java:195)
13971863: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
java.io.DataInputStream.readFully(DataInputStream.java:169)
13971864: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
com.cisco.Ged188.io.CRACTIInputStream.readMSG(CRACTIInputStream.java:570)
13971865: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
com.cisco.wf.subsystems.ctiserver.ClientConn.run(ClientConn.java:71)
13971866: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
com.cisco.executor.Thread.run(Thread.java:539)
13971867: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
com.cisco.executor.impl.ExecutorStubImpl$RequestImpl.runCommand(ExecutorStubImpl.java:690)
13971868: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
com.cisco.executor.impl.ExecutorStubImpl$RequestImpl.run(ExecutorStubImpl.java:486)
13971869: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
com.cisco.executor.impl.ExecutorStubImpl$RequestImpl.run(ExecutorStubImpl.java:762)
13971870: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:776)
13971871: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
com.cisco.executor.impl.PooledExecutorStubImpl$1$WorkerImpl.run(PooledExecutorStubImpl.java:99)
13971872: Jun 28 08:56:59.269 BST %MIVR-ICD_CTI-3-EXCEPTION:at 
com.cisco.util.ThreadPoolFactory$ThreadImpl.run(ThreadPoolFactory.java:853)

The user isn't able to login at all, and in fact see the same behaviour as 
described in this port:

[cisco-voip] Jabber with MeetNow and WebEx - Personal Room not compatible, now it is...

2017-07-05 Thread Lelio Fulgenzi 

I was testing out Jabber with MeetNow (and webex) and found that it gave me an 
error saying that my configuration was not compatible. I had a similar problem 
with Outlook MeetNow feature. It turned out that when you have "use Personal 
Room for meetnow" it doesn't work.

Let me rephrase that - it didn't work. In the case of outlook, turns out an 
overnight upgrade to WebEx fixed the bug. So me trying to replicate it was a 
lesson in futility.

But in the case of Jabber, it didn't work, then I confirmed by unchecking the 
personal room, meetnow worked. I went back and forth maybe once or twice, 
logging out, resetting, etc. But then once, when it didn't work, I changed it 
and tried meet now without logging out of Jabber, and then it worked, and now, 
I can't get it to NOT work any more.

I know I'm sounding crazy - anyone see this before?

I need to be able to replicate it in order to know how to fix it.

Lelio


---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

<>___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip