Santiago Londoño

Dear Sir, We have developed a small service that is able to receive and extract the information contained into the midnight reports sent by SnomOne (both, CDR and ACD reports), with that information, the service creates CSV files and forwards them to the customer's e-mail. Please contact us in case you are interested and would you like to see a demonstration: slondono@vertical.com.co Thank you!

Hi, We have a software called CallScout developed for PBXnSIP which I believe serves your needs. The link for the demo is: http://callscout.vertical.com.co/callscout DEMO OVERVIEW Demostration data corresponds to a fictitious company called Demo. This company is equipped with a Pbxnsip IP PBX, which has two domains defined: Demo Sales and Demo Research. Each domain receives and sends calls through a set of trunks. Demo Sales has two trunks, called Local and Global, while Demo Research has also two trunks, called PSTN and International. Demo Sales domain has three extension accounts: 2010, 2011 and 2012, and Demo Research comprehends the extension accounts: 2001, 2002 and 2003. ACD agents can login using any of these extensions, in order to catch calls received on Agent Groups. Both domains, Demo Sales and Demo Research, have an Agent Group defined, with account number 100. USERS The following demo users belong to each one of the existing roles and are available to access the application: Enterprise rol: Has access to all domains, trunks and extensions of the Demo enterprise. Login: demo-enterprise Password: demo Domain rol: Has access to all trunks and extensions defined for its assigned domain. For domain Demo Sales: For domain Demo Research: Login: demo-sales Login: demo-research Password: demo Password: demo Trunk rol: Has acces to calls coming into and from its assigned trunk. For trunk PSTN of domain Demo Research: Login: demo-research-pstn Password: demo Extension rol: Has access to calls made from and coming to its assigned extension only. For extension 2001: Login: demo-2001 Password: demo

Greetings, We have Pbxnsip hosted on a Linux server. Calls come from a E1 line to the PBX through a Sangoma NetborderExpress card and are attended in a Agent Group with aprox. 5 agents logged in. The PBX had been running for 8 months with no problems, but this week calls stopped ringing to agents. We checked the logs and the ACD always reported that all agents had a connected call, even when all agent extensions where free and ready to receive calls. Customers calling the Agent Group heard onhold music until timed out, just like when all agents are busy. The problem was solved restarting the Pbx process. Any ideas about how this could have happened?? Thanks!

Greetings, We have a CS410 appliance which restarts randomly once or twice each day. We tracked syslogs, but see no errors or locking reports before the system restarts, however, when the OS is booting, we received the following message on the syslog: WARNING : kernel: Bad eraseblock 7188 at 0x38280000 Could this be the problem? Has anyone else observed this behavior? Thanks in advance

Thanks a lot mate, that's just what we needed!

Greetings, We want to setup an IVR Node to just play a message to the caller. He should not be able to input any number, just hear the message and when the message is over the call should disconnect. Maybe we could use the !T!123! DTMF pattern, but what we need is to somehow, tell the PBX we don't want to transfer to extension 123, but to just disconnect the call. Is there any way to do this using IVR Nodes? Can we specify a .wav file to be played in the SOAP response to an IVR Node (instead of redirecting to an extension, just play a .wav file)? We have achieved a similar functionality using an Auto Attendant and its Hangup Timeout option, but we feel that it's not the best way to go. Thanks a lot!

Hello, We had a similar issue and the cause was that the SOAP request was malformed. Check if your code is adding any additional headers to your request or altering its structure somehow. (You can use Fiddler to see exactly how your request is being received by the pbx).

Hello, Another quite useful option offered by pbxnsip is that you can send CDR reports to an XML webservice and process them as you wish. For example, you could receive the CDRs in your webservice and store them in any database engine you want. Check this URLs for more info: http://wiki.pbxnsip.com/index.php/CDR#CDR_...AP.2FXML_Server http://wiki.pbxnsip.com/index.php/Processi...DR_from_the_PBX

Looks like he's spraying and praying. I received the same message

Greetings, We're currently doing this for Concursive CRM. We already have a couple of working examples.

That's right, we are receiving the queue status message and it works flawlessly. Is it there any way to tell the agent group which extension the call should be connected to? just as you can do with IVR nodes.

Greetings, In the Agent Group article of the pbxnsip wiki, there's a section called SOAP Interface: http://wiki.pbxnsip.com/index.php/Agent_Group This section says: "If you want to use external logic to control the queue behavior, you might want to use the SOAP settings. Please see the SOAP web page about this topic. " However, we haven't been able to find any details about how the topic. Has this not yet been implemented? Thanks in advance!

Digging into the forum I've found the answer to this question: "At the moment only indirectly. You can for example monitor the extension status for that agent." I think it would be nice if you can add the extension that picked up the call to the SOAP message issued when a calls connects to an extension of the Agent Group.

What we're trying to do is to find out which extension picked up the call

Hello, We had this same issue, we solved it developing an intermediate service, which receives the CDR messages and forwards them to all the recipients we want. Maybe it could work in your scenario too.

Greetings, We are trying to find the extension that just picked up a call received at an Agent Group. The PBX notifies us via SOAP when a call came into the Agent Group and when the call was connected, but these messages do not say anywhere which extension picked up the call. (Maybe this data should be contained in the Extension node of the SOAP message, when the state of the call is connected?). We have also tried querying the PBX database to get all the information available in the calls table, but we don't see where the extension could be. Making use of some programming and SIP buttons, we have been able to "guess" the extension which picked up the call, however, we feel that this way is not 100% reliable. Has anyone found a better way to get this data?

Looks like the PAC uses Internet Explorer configurations somehow, you just have to set Fiddler as your proxy server in IE and make sure that the Capture traffic option is active on Fiddler. (this must be done in the machine where the PAC is running).

This problem can be caused by a malformed SOAP response, the response that you send to the IVRInput request must have exactly the same format as the pbx expects. Consider using Fiddler to watch the response your application is sending. Pay attention to the Content length field, it must have the correct value. Check also whether the content is being sent chucked (Fiddler will show this too)

Hi! We have made some research about SOAP interaction with IVR Nodes: Editing the IVR Node properties you can specify a SOAP URL. The IVR Node will send SOAP notifications to this URL and you will be able to control the redirection of the call using sending the appropiate SOAP response. For more information about this topic go to: http://wiki.pbxnsip.com/index.php/Linking_..._to_an_IVR_Node The most interesting fact about SOAP interaction is that you can capture the data input by the caller using an external application and use it for your purposes. But, since these SOAP messages issued by pbxnsip have no WSDL (or we haven't found them yet), programmers can have problems accessing these services. We recommend using a simple Servlet to capture and respond to the SOAP messages issued by pbxnsip (if you are a java programmer), or using the HttpWebRequest object or sockets if you are a .NET programmer.

We have seen a strange behaviour when a call that just came out of an IVR Node enters an Agent Group. When a call enters an Agent Group directly, that is, the client dials the Agent Group extension, the pbx throws an IVRInput announcement indicating that a new call has entered the Queue. Then, when an Agent picks up the call, a SIP message is sent (if the Agent extension has a Monitor Extension button set up) saying that the extension is on a call (light on). This works fine, and is appropriate for agent group monitoring. However, a different situation arises when the call enters the Agent Group through an IVR Node (that is, an IVR Node redirects a call to the Agent Group). In this case the pbx throws an IVRInput message indicating that the new call has entered the queue. So far, so good. But as soon as the call is assigned to an Agent (the phone of the Agent starts ringing) the SIP message saying that the extension is on a call (light on) is sent. Note that, in this case the Agent has not yet picked up the call... Is there any explanation for this behaviour??

We have been making some tests involving different PAC versions, We have found that when a call comes to an extension through an IVR Node or Agent Group the PAC application is unable to figure out which extension received the call, therefore it exhibits a strange behaviour. We have noticed also, that usually PAC problems are caused by wrong button configurations or insufficient permissions for the account used by the PAC. For example, you must write the list of extensions you want to monitor in the field Watch following accounts on PAC of the PAC Account properties. (Curiously, that was not necessary on previous PAC versions). It is also quite useful to use a HTTP Protocol debugger, such as Fiddler while interacting with the PAC. This way you can watch the request and responses being sent and received by the PAC.