Hi All, just wanted to circle back to let you know we got this working.    Just to clarify for what its worth the symptom was Device not Accessible (I mistakenly reported Available).   Issue was the calling search space and mask on the RCP.  thanks again for your support! Great group here. ... View more

Marek and Bill handled this very well.   Only thing I would add from a simplistic explanation is call types can help you know who called (for what) and skill groups let you know who took care of it.  The CUIC CTSG reports help break that down. ... View more

Thanks Carla,  Bill and Marek are following along too, but wanted to get back to you. Glad you got the issue resolved with the dial pattern.  I must not be that far along..maybe having config trouble with my LCP ports.    Curious if you can log in using the LCP port extension (instead of a regular acd phone) in regular non-mobile agent mode?   I know it wouldn't be able to answer a call, but does it let you login?  Also can you login mobile agent mode nailed with a 7 digit pbx number?   Mine will let me login in call by call mode with the LCP DN, but fails when I use LCP as the extension in normal mode, and of course nailed mode.   thanks for your help! ... View more

Thank you Marek, Carla, and Bill ..will check it out the cm tool.  Have tried several device pools, partitions, and CSSs.. right now using the same config as a working SCCP phone for the LCP.  Good point about the mask, have tried a few different masks as well.   Unfortunately it didn't matter whether 10, 11, or 12 digit pstn target.   Bill got me thinking though about simplifying things to isolate, and it doesn't work using 7 digit on the call manager either...no pstn so don't think the mask is in play there.     Carla, curious if you can log in using the LCP port extension (instead of a regular acd phone) in non-mobile agent mode?  Mine will let me login in call by call mode with the LCP DN, but fails when I use LCP as the extension in normal mode. I know it wouldn't be able to answer a call, but does it let you login?  Also can you login mobile agent mode with a 7 digit pbx number?   thanks you all for your help over the weekend.. really appreciate it!  ... View more

Thanks Bill, appreciate it. I think that is one I stumbled across as well, but good to know I'm working with the latest and greatest - v9  :-)  Have sent an update to Marek with additional info if you're still interested. thanks again for your help!  ... View more

Hi Marek, Appreciate the detailed response.  I think you helped fill in some blanks for me.  Have made the following changes: - I Left LCP ports alone except tried a few different device pools. Seems always able to access the LCP ports, 5647700, 5647701.  The LCPs are still in the agent target rules and device target explorer ..not sure if that is necessary or redundant - I changed the RCP port DNs to 1181050, 1181051 - which are unused DNs that are part of the range the outbound dialer uses in case dial peers are set for calling number "118XXXX"; they are not in the ATR list, but did add to device target explorer...also not sure if needed for RCP. - Re-associated  both LCP and RCP ports with PGuser for good measure. - Turned up tracing to 3 on jtapi ..nice to have the system to myself on Saturday :-) -Tried to login with nailed connection using 5647700 and dial number 5083613005 (have also tried with "9, 91, and 1" prefix but our dialer lists are 10 digit so thought that would work) -After clicking the login button, Finesse goes into action and after a few seconds I see a very quick pop saying something to the effect of "We initiated a setup call to the number you provided. Answer the phone to complete the sign in process" Then almost immediately, Device Not Accessible, contact your system administrator.. yours truly  -From what I can tell in the logs it looks like a good portion of the config seems to be right..as you mentioned it looks like it is matching up the LCP and RCP and looks like the RCP port 1181050 is trying to make the outbound call.   Don't know if it was a red herring, but noticed the dial number entry somehow changed to seven digit (dropped the area code) during the call setup. Ultimately it looks like it fails with PlatformExceptionImpl caught: Could not meet post conditions of connect() which doesn't ring a bell with me but wild guess sounds like maybe the call setup is failing from the RCP port to the egress gateway.   Attached the jtapi log for any home gamer who might want to take a look.    Finesse web Services entry for the failure doesn't look interesting but just in case: [ENTITY_ID=1131340][ERROR_DESCRIPTION=errorCode 70][command_name=LOGIN]: Received failed command response 0526550183: 172.24.0.207: Mar 21 2020 13:14:19.917 -0400: %CCBU_COMMAND_POOL-28-worker-32-3-CMD_FAILED: %[ENTITY_ID=1131340][ERROR_DESCRIPTION=errorCode 70][command_name=LOGIN]: Received failed command response 0526571090: 172.24.0.207: Mar 21 2020 13:45:42.442 -0400: %CCBU_COMMAND_POOL-28-worker-33-3-CMD_FAILED: %[ENTITY_ID=1131340][ERROR_DESCRIPTION=errorCode 70][command_name=LOGIN]: Received failed command response 0526571949: 172.24.0.207: Mar 21 2020 13:46:57.556 -0400: %CCBU_COMMAND_POOL-28-worker-34-3-CMD_FAILED: %[ENTITY_ID=1131340][ERROR_DESCRIPTION=errorCode 70][command_name=LOGIN]: Received failed command response   Thanks again for your help!         ... View more

Thanks Omar, have the desk settings set at optional.  Agent can choose either. ... View more