Jump to content

Pradeep

Members
  • Posts

    70
  • Joined

  • Last visited

Posts posted by Pradeep

  1. Currently, it is done for a reason. But in the future releases we will make it settable.

     

    Hi there,

     

    Another question about the PAC:

    Is it possible to start this application without the question of verifying the ip-address of the PBX?

     

    Kind regards,

     

    Rene.

  2. We are working on the installer

     

    he guys amazing....

     

    amazing guys, finally...

     

    requests:

    - lets include the address book dialer posted on this forum.

     

    creating install package:

    1. download apple developer tools

    2. in /Developer/Applications/Utilities/Packagemaker.app is your friend.

     

    no clue about the time issue.

     

    christof

  3. Javascript validation did not consider the :port option. We will fix it ASAP.

     

     

    Testing the 3.0.0.2992 for the CS410.

     

    On the Edit Agent Group

     

    SOAP Interface:

    Queue Status URL: http://192.168.1.100:10000

     

     

    In the past I was able to put a port number on the end of the URL.

     

    Now I get an error and it won't allow this.

  4. The blockview/buttonview is no longer supported. Sorry! If there something specific that you were looking for that is missing?

     

    I am only receiving a Treeview of the Extensions.

     

    Can I get the original "Blockview" back?

     

    Bill H

  5. Agent group support is not there yet. But it is in the works.

    In the previous version, just the queue was visible but was not doing anything. So till it is completely supported, the display is removed.

     

    I just installed version 1.9.2.19 and tried to monitor the queue of an agent group.

    But nothing shows-up in the console.....(exept extensions and lines).

     

    With a previous version (1.9.1.0) the queue is visible.

    Am i doing something wrong here ??

     

    Thanks,

    Rudi

  6. Will consider this request for future releases (dates not decided yet)

     

    After presenting to a customer how his remote sites can be networked together with multiple PBXnSIP systems, I came to realize that the PAC will only monitor one of these systems at a time. Is it possible to set it up in a way similar to outlook where you can have it check several accounts at once (or in this case phone systems). It would also be nice if the PAC would remenber it's previous window size, and position on the desktop.
  7. Follow these steps

     

    1. Create a trunk first

    2. On the dial plans page, create a new dial plan

    3. Edit the newly created dial plan

    4. Enter some number on the 'pref', select the trunk name (from step 1), then use 0* for pattern, use 0031* for the replacement.

     

    Hope this helps

     

     

    Hi. I tried to understand it by reading manual and wiki but I can't.

     

    What I want is :

     

    10-digit numbers

     

    for e.g. 0101234567 -> 0031101234567 (leave the 0, prefix 0031*)

     

    7-digit numbers

    for e.g. 1234567 -> 0031201234567 (prefix 003120*)

     

    How do I do this?

     

    Thanks in advance.

  8. We have created a wiki page for the schema definition for the CDR.

    http://wiki.pbxnsip.com/index.php/Processi...DR_from_the_PBX page explains about the SOAP CDR and http://wiki.pbxnsip.com/index.php/Cdr.xsd show the schema definition.

     

    WSDLs are generally needed only if we(PBX) provide any web services APIs. Since we do not expose any web service APIs, WSDLs are not needed.

    XSDs are required for the use of web services APIs(for passing arguments and return values). So in our case it too is not needed, but we can probably define the XSDs and make it available for you.

  9. WSDLs are generally needed only if we(PBX) provide any web services APIs. Since we do not expose any web service APIs, WSDLs are not needed.

    XSDs are required for the use of web services APIs(for passing arguments and return values). So in our case it too is not needed, but we can probably define the XSDs and make it available for you.

     

     

    I need the XSD and WSDL definitions for tje SOAP XML coming from the PBXnSIP PBX so I

    can build a listener service to insert the CDR data into a SQL database.

  10. Victor,

    You should not be seeing this error if you are running 1.9.2.16 (if you are referring 'ssame behaviour' as the error shown in jlumby's posting)

     

    I'm getting the exact ssame behaviour
  11. We are running on Vista and 2003 server without these issues. We will run some test on XP.

    Just curious, how many extensions are configured in the button profile? Also, system configuration-memory, processor info, CPU load(if lot of other processes are running) etc will be useful.

     

     

    i agree - locks up all the time... on windows XP - running 1.9.2.12
  12. Can you see what the version is displayed under Settings tab?

     

    I have been demoing the Beta version of the PAC, and have noticed some issues. The first is that the download link says it should be version 1.9.2.0 however when I install it I get 1.9.1.0

     

    Beyond that I have found that it often gets out of sync with what the extensions are actually doing. It will show that extensions, as well as trunks are in use when they are not, and transfering to an extension will often light up the wrong extension. The longer it is running, the worse it gets. Closing, and reopening the application always clears up the issues.

     

    I have also found that when registering the PAC to certain extensions it fails with a long error message (see attached file for error message). I cannot figure out why registering to other extensions is not a problem

  13. We wanted to move away from the button/extension view.

    In the tree view, we still have the extensions, lines (agent group, conference etc, future)

     

    I updated to a new version of the PAC Version 1.9.2.12. I don't have my extensions tab anymore. The only tabs are treeview, settings, messages. Everything is still working fine. Is the extension view not supposed to be in this version?
  14. There is no theoretical maximum for the monitored extensions. We have tested with 40+ extensions.

    Could you please monitor the CPU load?

     

    Is there a maximum number of monitored extensions (or theorhetical maximum) -

     

    I'm attempting to monitor 12 extensions, but the console keeps locking up on me, especially with ext. to ext. calls.

     

    Using the latest console version.

  15. Extensions have state associated with them. What you see are the different states of the phone/user agent. Below are the possible values.

    ready - phone is registered and ready for the use

    offline - not registered

    logoff - agent is logged off

    dnd - phone has the 'do not disturb' set.

     

    Ok, I might be being a bit thick, but just installed the PAC and it looks good, but on my console some of the extensions have "logoff" and others have "ready" next to them. What does that mean?? :)
  16. Tom,

    If I understand correctly, you are trying to send the fax from HT268 or a Kapanga fax phone that is registered with the broadvox. Also, I assume that broadvox has a sip trunk to pbxnsip and pbxnsip has connectivity to the MS exchange server.

    Can you please confirm that this is what you have in your setup?

    Pradeep

  17. I uninstalled the pac that I had on my pc. I then installed the version from the link in the previous reply. I still don't have anything showing up in my extension tab. Also, after I installed the pac the version is still showing up as 1.9.1.0. I am running 2.2.1.2757 (Win32) Version of pbxnsip

     

    This is the error I get in the messages tab of the pac console. I don't get an error message at all if I don't assign the pac extension a configuration profile

     

    Message type :ERROR received at :4/30/2008 10:39:22 AM

    -----------------------Begin Message------------------------

    System.FormatException: Input string was not in a correct format.

    at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

    at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

    at System.Int32.Parse(String s)

    at AttendantConsole.MainForm.send501(String message)

    -----------------------End Message--------------------------

     

    Hi towns,

     

    Could you please the change following settings on your PBX ?

     

    Under "Settings->General" page go to "SIP Settings" section. Select radio button "Long" for "Use Short SIP Headers" and hit "Save".

     

    Now restart the PAC. Let me know how it goes.

     

    Pradeep

×
×
  • Create New...