Jump to content

centricall

Members
  • Posts

    44
  • Joined

  • Last visited

Posts posted by centricall

  1. Thanks for reply.

     

    I have another question.

     

    The Ring Stage Duration is 10 seconds and the Max Ring Duration is 30 seconds. So, the agent group send the call to an agent and rings on this agent during ring stage duration and then adds an agent and so on.

     

    I want the Agent Group to ring only one agent at a time. So, I set the Max Ring Duration to 10 seconds. But the problem is outgoing calls hang up after 10 seconds.

     

    Setting the ring stage duration to 30 seconds can be a solution but this period is a very long time and not acceptable.

     

    What can i do to ring only one agent at a time?

  2. Hi,

     

    Is there a way for delivering next incoming call while early incoming call is ringing? (this question is for both hunt group and agent group)

    For example; there are two incoming calls. One of them delivered to an agent. And It is ringing on the agent.

    During this time , I want pbxnsip to deliver the second incoming call to an agent without waiting the early call to be connected the agent.

  3. We have already set the agent recovery time to 5 seconds. It is reasonably small value. We will analyze the logs.

     

    We have already set the Caller Priority to Queue Entry Time.

     

    Does the agent group not distribute the second call in the queue to an available agent when the first call in the queue ringing on an agent and not accepted?

     

    Could you please answer this question?

  4. Hello,

     

    We have two major problems about Agent Group.

     

    First one : sometimes there is a blockage when Agent Group distributes calls to the agents. Although there are many available agents and there are many calls waiting in the queue, these calls are not distributed automatically to the agents along 2 or 3 minutes. It begins to distribute then.

     

    When the first call in the queue ringing on an agent and not accepted, does the agent group not distribute the second call in the queue to an available agent?

     

    The second problem: sometimes agent group distribute multiple calls to an agent when the agent is on the line with another call, eventhough the Allow multiple ACD calls on agent - even if busy: No selected NO. Could you have any suggestion about this issue?

     

    We need immediate help.

     

    Thanks in advance.

  5. Generally, the default values are already set internally. But if you want to change them, then you can go and choose one from the respective drop-downs.

     

     

    The values on the dropdown list are not usable for us. For example i can not set the agent recovery time to 1 or 2 seconds (it is possible on version 3). How can i set the Max Ring Duration from the Admin settings to below 30 seconds? (the minimum value on the dropdown is 30)

  6. There was an issue calculating the $(talk_duration). We will fix that.

     

    But the $d, $(duration) and $(ext_duration) should still work fine.

     

    The log from the testing we have done here shows that.

     

    [8] 2011/10/11 17:28:18:	The cdr format string is $w$5e$12c$5d$5A$5(duration)
    [9] 2011/10/11 17:28:18:	SOAP: send CDR to cdr:10.20.14.195
    20111011172808 70 19 7 19
    

    As you can see $d and $5(duration) both produced 19 as the output.

     

     

    [8] 2011/10/11 17:30:08:	The cdr format string is $w$5e$12c$5d$5A$5(extn_duration)
    [9] 2011/10/11 17:30:08:	SOAP: send CDR to cdr:10.20.14.195
    20111011172956 70 21 7 21

     

    As you can see $d and $5(ext_duration) both produced 21 as the output for a different call.

     

     

    When will this issue be solved?

     

    Thanks.

  7. That but is fixed on .4025 version. Please pick your version from http://www.pbxnsip.com/download-software/software.php. Make sure to back up before the upgrade as a general practice.

     

    We upgraded our system to .4025 by getting new licence but TalkDuration field in the CDR file always zero. We have to get this data. Moreover, ExtnDuration field sometimes is negative like -16748.

     

    Could you help us about this issues?

  8. I need to determine whether the calls reached the call-center agents (and how long were they engaged in that call) or whether the call has been abandoned by the caller.

     

    Call scenario is: PSTN >> SIP Gateway >> IVR >> Agent Group >> Agents

     

    We have just upgraded to V3 and are starting to use it with the MySQL connectivity. I have enabled all the '$' options on the cdr except the cmc. If you analyze the table by simulating calls reaching and engaging the agents and calls being abandoned by the caller, I see no difference on the data it writes on the table.

     

    In the table, there are the fields talk_duration, duration, extn_duration. They give me the same data, identical numbers for inbound and outbound calls, and whether the agents receive the calls or whether caller hangs-up before talking to the agents.

     

    Anything I may have missed? Should I be getting different numbers in there?

     

    Anybody who can point me to the right direction?

     

    Thanks in advance.

     

     

    Mel Guevarra

     

    Hello,

     

    We are developing a call center software and it is almost the same problem we have. The TalkDuration field always zero in the CDR file about the call. Can you help about this issue?

     

    Thanks.

  9. What I meant was setup your email address and after 5-6days (or whenever the PBX "crashes"), you can collect nightly status emails and send them to support@pbxnsip.com

     

    Another point to note: Remember that PBX keeps the CDRs in the system for the duration specified by "Admin->Settings:Keep CDR Duration". So, it is normal to see the increase in the memory usage to certain extent. But it should not keep growing forever.

     

    Ok , we will forward you the e-mail. Beside this ,now, I will send you task manager and process explorer cpu and memory records via e-mail.

    My mail address is hasanali.eris@bilgisistemleri.com.tr. So, You can distinguish my e-mail adress

  10. Oh. 3.4 did not support 64 bit yet.

     

    Maybe you can consider upgrading to version 4. There are many features, but also many bugfixes in version 4, including the option to run 64 bit! If you can, create a small testinstallation with version 4 and see if you can smoothly upgrade: If you did nothing special, the upgrade should be easy.

     

     

    We had no option to upgrade 4.0. Because of this, we have installed pbxnsip on to 32 bit xp machine. But , again, we've encountered the same problem,memory is still increasing. I think this problem is not releated with 32 bit or 64 bit. Beside this ,I wanted to send you pbxnsip process information via excel document, but your system does not let me upload excel file as a attachment.

  11. There is a problem is you have too many HTTP or SIP traffic on TCP/TLS. This is because the PBX forks a thread for each of them. In such cases, you should use the 64-bit version of the PBX, which has enough virtual memory address space to for enough threads. (One thread takes usually about 10 MB in the VM, so that with 200 threads you are already taking 2 GB, which is pretty much all you have in 32 bit).

     

     

    Is there 64 bit adition for 3.4 version pbxnsip. Because our application written for this 3.4 version , we could not find 64 bit for this version.

  12. We have 32 bit and version 3.4.0.3201 (Win32) pbxnsip service set up on windows server 2003 64 bit standart edition,

    And the memory used by pbxnsip service increasing very fast, it crashes once in 5-6 day . In this location call traffic is very high.

     

    But we have 15 different location that use same version of pbxnsip, but all of them does not have crush and memory problem.

    and generally, Pbxnsip service set up on 32 bit windows beside these, call traffic on these locations are not as much as the location above.

     

    What can be the reason for this, please help us?

×
×
  • Create New...