locked
RCC - incoherent starting status in systray RRS feed

  • Question

  • Hi

     

    RCC is working well between OCS and CUPS (or GETS, experienced the same).

    But at the Communicator launch, the Communicator systray icon shows a warning, and if you put the mouse on it, it says "Phone integration error", which is not true.

    As soon as you change status, the warning disapears.

    Does someone have not this starting behaviour ?

    It sounds to me like a timer issue (RCC is slow to set up at Communicator start, and systray maybe displays statuts "too soon" ?)

    Saturday, December 6, 2008 5:39 PM

All replies

  • I didn't see that in our most recent OCS<>CUPS integration; none of the clients showed integration errors.
    Saturday, December 6, 2008 7:48 PM
    Moderator
  • Hi,

     

    Did you specify the MAC address in the tel URI ?

    I did not.

    I use Mobility Profile, but I saw the same behaviour with Phone profile monitoring.

    It seems that if your end user is associated with more thant one device (hard phone + IP Comm for example) you have this warning message. If only one associated, no message.

    Monday, December 8, 2008 10:02 AM
  • I have the same issue with GETS and the same comment.
    In Communicator log there is a Kill Timer error but with no more information.


    But for the moment no solution for me.. If you have any idea.
    Tuesday, December 9, 2008 10:32 AM
  • Hi Jeff,

     

    Could you please compare or share an RCC Communicator log file with this if you have one ?

     

    here is Communicator start log extract relating to timer:

     

    Just after the CSTA/SIP GetCSTAFeaturesResponse:

     

    12/03/2008|17:15:31.603 C04Big Smile8C WARN  :: SIP_CALL:Tongue TiedtartSessionExpiresTimer Session-Expires header value is LESS than: 720
    12/03/2008|17:15:31.603 C04Big Smile8C TRACE :: SIP_CALL:Tongue TiedtartSessionExpiresTimer starting session timer for 600000 sec, this 0370EC58
    12/03/2008|17:15:31.603 C04Big Smile8C INFO  :: CUccRemoteCallControlEndpoint::NotifyMessageInfoOperationCompletion - Handling response GetCSTAFeaturesResponse
    12/03/2008|17:15:31.604 C04Big Smile8C ERROR :: CUccRemoteCallControlTransaction - KillTimer failed 0x0

     

    And after the MonitorStartResponse:

    12/03/2008|17:15:31.808 C04Big Smile8C WARN  :: SIP_CALL:Tongue TiedtartSessionExpiresTimer Session-Expires header value is LESS than: 720
    12/03/2008|17:15:31.808 C04Big Smile8C TRACE :: SIP_CALL:Tongue TiedtartSessionExpiresTimer starting session timer for 600000 sec, this 0370EC58
    12/03/2008|17:15:31.808 C04Big Smile8C INFO  :: CUccRemoteCallControlEndpoint::NotifyMessageInfoOperationCompletion - Handling response MonitorStartResponse
    12/03/2008|17:15:31.808 C04Big Smile8C ERROR :: CUccRemoteCallControlTransaction - KillTimer failed 0x0
    12/03/2008|17:15:31.808 C04Big Smile8C INFO  :: CUccRemoteCallControlEndpoint:SurprisenChannelStateChange - enState=1->2,status=0x0,text=(null)

    At the complete end of log (wait without actions on Communicator):

    12/03/2008|17:15:32.290 C04Big Smile8C ERROR :: SIP_STACK::MapDestAddressToNatInternalAddress m_pDirectPlayNATHelp is NULL.  Setting *pIsDestExternalToNat to FALSE
    12/03/2008|17:16:02.002 C04Big Smile8C INFO  :: CUccRemoteCallControlTransaction::HandleTimerExpire - EventSession=00000000,TargetSession=00000000,OperationType=16384,TargetState=1,ResponseRcvd=1,EventRcvd=0

    Do you get the same "killtimer failed" ? could it be related ?

    Tuesday, December 9, 2008 9:44 PM