このページは役立ちましたか?

エージェント毎にDNDの時間をレポートできますか?

    目次
    ヘッダーがありません

    It's not possible to generate a report on DND time. 

    The technical reason lies in the way that SIP defines the method for DND.

    When a SIP phone activates DND status, the phone will respond to all requests for call creation (essentially "ringing") with a 603 status message.  The 603 is defined as such:

      The callee's machine was successfully contacted but the user
      explicitly does not wish to or cannot participate.  The response MAY
      indicate a better time to call in the Retry-After header field.  This
      status response is returned only if the client knows that no other
      end point will answer the request.
    

    As a result of the 603, the system will send the caller into the user's voicemail or some other routing action can be accomplished.



    The reason you can't get a report is:



    The 603 status message is only

    sent

    to the system

    when the system tries to contact the phone

    .



    There is no "announce" as it were within the SIP stack.  So when you press the DND button on any SIP phone, the phone

    doesn't actually tell the system it's on DND



    You could press the DND key at 10 am, walk away to a meeting, and when someone tries to call you at 10:30 am, this is the first time the

    system

    is aware that your phone is on DND.  That's 30 mins of unreportable time!



    It gets worse.  The system doesn't

    remember

    a 603 code!  So in a report, all you would see is "User on DND from 10:30 am to 10:30 am." 



    The system wouldn't flag the phone as being on DND and continually check to see if this status had been deactivated.



    This is a fundamental issue with the SIP stack - it's not specific to Fonality.  The SIP stack is maintained in RFC 3261 by the IETF (the body of governance over protocols and communications standards that affect the entire Internet).  Vendors (like Fonality) are responsible for implementing the SIP protocol consistent with RFC 3261.  Changing any aspect of the SIP stack means we would be breaking with "standards compliance" which is something that no vendor wants to do lest they risk their inter-operability with manufacturers of other SIP devices - like phones.

    このページは役立ちましたか?
    タグ (タグ編集)
    • No tags

    ファイル 0

     
    あなたはコメントを投稿するには ログイン しなければなりません。
    Powered by MindTouch Core