Jump to content

Mads Mortensen

Members
  • Posts

    134
  • Joined

  • Last visited

Posts posted by Mads Mortensen

  1. Yes. There are a couple of enhancements of the queue.

     

    BTW the ACD is now also able to ring an extension forever, it necessary the whole night.

     

     

    I have been testing the part with ACD - I still cuts the call after apx. 90 mins. calling....

  2. Thanks for the feedback. We will take care of it in the next versions.

     

    Meanwhile, you can manually -

     

    - Change "max_regs" to the number you want under pbx.xml file.

    - Change "mb_pinsize" under "<working dir>/domains/1.xml" file. Note that if you have multiple domains, make changes to the proper xml file.

     

     

    Where can I download the BETA of ver 4 ?

  3. Looks like you have some old button lists in the system. Please check out the "button_lists" folder under the PBX install directory. If the "name" field is empty in any of those files within that directory, that can cause this issue. You can delete those files and the problem should go away. You may have to restart the PBX.

     

     

    Works!!!

    Perfect!!

  4. What version are you running? 3.3.1.3177 should be doing this.

     

    You can also try the "BLF" mode, just to see if anything changes.

     

    There was a problem history when you changed names in the domain because that could break the links in the button definition; however that should also be fixed in 3.3.1.3177. Maybe you need to hit the save button again on the button web page to update all links.

     

     

    Yes, I am running lastet ver (3.3.1.3177) - I have tried to hit "save" again (and again and again) but no luck.

    I have tried to change to "BLF" mode, but nothing changes!!

     

    Futher more, there are also issues with the agent login/logout button.

    Actually, the buttons the works perfect everytime (after restart) is "line" & "speeddial"

     

    The button profile under the user "user login / button setup" - only works 1 out of a 100 times!!

     

    Sometimes everything works, after a restart, only the line keys & speed dial works.

     

    This is some MAJOR issues.

    I really need to have this solved ASAP, as the customers are complaining!! (we are running hosted solutions)

  5. Hi

     

    normally we have no problems using PnP

     

    But we have one customer in special, which have problems;

    We can PNP:

     

    Lines

    Speeddial

     

    But NOT monitor Ext. on phone...

     

    Any help?

     

    PS! We are using a Hosted solution, with several domains, and it is only in one domain, where there is a problem; Could there have gone anythinh wrong when adding the domain???

     

     

     

    Anyone with a solution for this??????????

    I can furthermore add that it is status LED (ext. status LED) that do not PnP corretly!

  6. OK. What happens, if you create more button-profiles? Are they added to the empty fields or will some of the empty fields be renamed? Maybe a cleanup of the appropriate xml-File is necessary ;-)

     

     

    Tried all that - but nothing of that seems to help.

    Futher more, I think that is is somehow causing some problems in the PnP config, that is why I want to remove them.

  7. Hi

     

    normally we have no problems using PnP

     

    But we have one customer in special, which have problems;

    We can PNP:

     

    Lines

    Speeddial

     

    But NOT monitor Ext. on phone...

     

    Any help?

     

    PS! We are using a Hosted solution, with several domains, and it is only in one domain, where there is a problem; Could there have gone anythinh wrong when adding the domain???

  8. Hi

     

     

    I can without any problems make button PnP work (monitor extensions, private lines etc.) work, if I set it up as an admin.

    BUT if I login as a user, an want to config OR change my button setup - It do not work.

     

    What can be wrong??

     

    We are using newest ver. of PBXnSIP with SNOM phones.

  9. Well, if you keep the default value "Entering the Agent group" for "Event for connecting the call" AND "Regular ringback when agent rings" for "Ringback tone" (the very next field), you will achieve what you want. But as 'pbxnsip' mentioned in one of the earlier responses, the caller will be charged from the beginning. With these settings, the caller will be connected at the beginning itself, the 90 seconds issue will not arise.

     

     

    I know all this :-) :-)

    But I might not see where the issue is located, BUT, from what I can read from all this, is, that it is VERY IMPORTANT that persons there is NOT ready/at their desk to answer calls, logs out from the agent group.

    If they log out (and there is no handset ringing) as the handsets that is logged in is talking, the calls will NOT drop. Correct???

  10. Can you increase the log level to 8 and send us the log for this case? something does not seem right. Also, can you tell us what is set in "Event for connecting the call" field for the agent group?

     

     

    The field is set for: "Agents picks up call"

    I will send the log.

  11. Does the ACD connect the call (meaning: does the caller have to pay for the call)? There is a option that tells the PBX to connect the call only when the agent picks the call up; but for a busy group that is usually way too long. What is the event for connecting the call?

     

    If the handset is ringing for so long you should redirect the call out of the queue, for example into a hunt group. It is just not good to keep the handset ringing for so long. You might even redirect the call back into the same ACD; customer will not be amused to get kicked back into the queue (especially at the beginning of the queue!!!) - but this is still better than a dropped call.

     

    The second you enter the ACD, you hear music while wating.

     

    I understand that when the handset rings, to long a ring time is a problem.

     

    BUT the problem is ALSO when every handset is busy, and you have to wait that an agent becomes ready to take a other call.

    That means, that even when no handset is ringning (they are all busy) the call still only stays in the ACD 90 sec.

    And let be honest, a waiting time in a supportgroup, can be longer than 90 sec.

×
×
  • Create New...