Jump to content

Search the Community

Showing results for tags 'JSON'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • App Topics
    • Android App
    • iOS App
    • Windows App
    • MacOS App
  • News
    • Announcements
    • New Features/Versions
    • Product/Site Comments
    • Polls
  • Using the PBX
    • Using Cell Phones
    • Web Interface
    • Call Treatment
    • Call Recording
    • Security
  • Marketing Exchange
    • Customer Research
  • Product Setup
    • General Setup
    • Best Practices
    • PAC and WAC
    • Trunk Setup
    • Dial Plan Setup
    • Extension Setup
    • Mailbox
    • Conference Room Setup
    • Auto Attendant Setup
    • IVR Node Setup
    • Agent Group Setup
    • Hunt Group Setup
    • Calling Card Setup
    • Paging Setup
    • Service Flags
    • Music on Hold
    • SOAP
    • SNMP
    • Embedded
    • Linux-related Topics
    • Windows-related Topics
    • MacOS related topics
    • FreeBSD-related topics
    • CDR
    • snomONE Plus
    • Virtual Appliances
  • Connectivity To Other Services and Components
    • Gateways
    • ITSP's
    • VoIP Phones
    • Microsoft Interoperability
    • Integrations
    • SMS Inbound / Outbound Settings
    • Email Topics
    • Fax Setup
    • Firewalls and NAT
    • Hosting
  • Non-English
    • French
    • German
    • Spanish
  • Business Topics
    • Service Providers that support the Vodia PBX
    • Integrators
  • Other
    • PBX Lounge
    • Question About The Forum
  • Partner Area
    • General Topics


  • Community Calendar

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start











Found 4 results

  1. Buen dia: Hemos desarrollado una aplicacion en PHP para poder recibir los JSON del pbx Vodia. empieza funcionando bien, despues de un tiempo ya no envia mas informacion al cdr remoto. el log solo se queda con la siguiente leyenda: [6] 20170316201930: 283 more requests pending to gnpqtfbz.cjp.mx:443 reiniciamos el server y vuelve a enviar. pero perdemos toda la informacion. que recomiendan para solucionar esta situacion. Saludos, Cesar Bagatella
  2. Would like to hear from anyone on this list that is able to send a complete webcdr json record to a remote server and receive the entire record. I was able to capture a few complete records using tcpdump on the remote server, but more often than not, I am only getting partial records, As a test, I also ran tcpdump on the Vodia server and the remote server to compare output. The record being sent from the Vodia server was also incomplete, so the remote server showed the same info. I'm wondering if I have my tcpdump filter set up incorrectly (I am using -s0 for full length records) or if the Vodia server is cutting off the record for some reason. My tcpdump filter is working fine with plain json posts, just not webcdr json posts. I'm having no problems with the plain json records sending and receiving, so this webcdr json is confusing me. Any ideas? Thanks, Craig
  3. Hi, The value of being able to evaluate, or at least to have a yardstick to assess the effectiveness of a SIP Trunking supplier (for call termination) is rather obvious (or so I think), so I will not elaborate on that. There are a few parameters to do so and some of them we can rather easily get from the PBX. The ones that can give an idea and we can get rather easy are the following: 1) Average call duration 2) Estimated MOS of calls 3) ASR (Average Seizure Rate, which is just the percentage of completed calls of all those attempted) The one that would be very useful and the ingredients to have it may already be there but I do not know how to get is the following: 4) NER (Network Efficiency Ratio). This one, is like ASR, but taking away the calls that did not complete because of reasons not accountable to the carrier (or SIP Trunking Call Termination Supplier). Those reasons to not complete a call that are not the responsibility of the supplier are: 1) The call was ringing, but no one answered 2) The recipient was busy 3) The receiving carrier answered with an error code (or recording) of their own This NER would be the truer measure of the effectiveness of a call termination supplier. The percentage of successful calls terminated taking away the effect of those calls not terminated because of reasons out of the suppliers reach. I bet that the PBX has the ingredients to estimate NER, or at least allow us to gather them so we can estimate it. I believe that all those things can be gathered from the JSON CDRs, but I do not know how. Currently, we have been successful getting sufficient information from JSON CDRs for billing purposes, but we are rather lost about getting other kind of information from it and I suppose we could. Can we get guidance on these topic? Regards
  4. *Resolved*
  • Create New...