Register Terminal with SIP Phone

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • hofmad
    Hot Shot
    • Sep 2014
    • 14

    Register Terminal with SIP Phone

    Hi there,

    when I try to use "RegisterTerminal" together with "Dependency Mode" set to "Dependent" on a SIP station it always returns the error:

    Code:
    Registration Reject reason: resourceUnavailable
    Shared control denied because the DCP phone is out of service
    It is working with a H.323 station when 1xC is registered.
    Is there a way to register a SIP extension the same way?

    With "Dependency Mode" set to "Independent" it is working, but this will consume an extra license.

    Thanks.
  • jtb1
    Whiz
    .
    • Feb 2017
    • 33

    #2
    "but this will consume an extra license." what kind of license do you think Independent mode consumes that dependent mode does not?

    With SIP stations, you must use Independent mode when you register a DMCC device against the extension per standard DMCC practices.

    Comment

    • hofmad
      Hot Shot
      • Sep 2014
      • 14

      #3
      Ok, I'm using an AES 10.2 within the 30 Days while everything is free and didn't check on the Live-AES for needed Licenses :-/

      Is there a way to recive the Button status of a station without registering it? I just need to get the current status of the "hunt-aux" button (active/inactive or light on/off)... or is there a way to get the current availability status of every hunt-group member (not a skill, no agents!)?

      Thanks.

      Comment

      • jtb1
        Whiz
        .
        • Feb 2017
        • 33

        #4
        The only methodology I am aware of to get status information (hunt-aux) is through a DMCC Device monitor - and that will not work for SIP stations (it is only supported for legacy DCP and H.323 devices). You can only do third party call control services (and receive media) with SIP stations using DMCC (or any other AES API). You could investigate if there is some SAT capability to get status information - or perhaps use vu-stats to get information. We don't work with non-ACD hunt groups much, so there are various details that we may be unaware of that have been built into the product.

        Comment

        • hofmad
          Hot Shot
          • Sep 2014
          • 14

          #5
          Thank you for your answer. The problem is, that even ASA/SAT can't show the current status of every Hunt Group member. With the dadmin User (BP Login) you can execute "display internal-data [hg]" and see a maximum of 10 members with their availability status (y/n), but not more... and AES SMS doesn't support dadmin login with passwort and PIN.

          Thank you.

          Comment

          Loading