Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by chaddow

  1. That isn;t picking up the call and sending it out the toll-free-outbound trunk that is selected. the call is going out the carrier-outbound trunk. pref: 25, trunk: toll-free-outbound, pattern: 1?(8(00|55|66|77|88)[2-9][0-9]{6})@.* , replacement: 1?(8(00|55|66|77|88)[2-9][0-9]{6})@.* pref: 100, trunk: carrier-international, pattern: 011* , replacement: 011* pref 1110, trunk: carrier-outbound, pattern: * , replacement: *
  2. Is there a a 1 line pattern match and replacement for Vodia that puts all of this in one line/one trunk? pref: 40, trunk: toll-free outbound , pattern: 800* , replacement: 800* pref: 44, trunk: toll-free outbound , pattern: 1800* , replacement: 1800* pref: 50, trunk: toll-free outbound , pattern: 888* , replacement: 888* pref: 55, trunk: toll-free outbound , pattern: 1888* , replacement: 1888* pref: 60, trunk: toll-free outbound , pattern: 877* , replacement: 877* pref: 65, trunk: toll-free outbound , pattern: 1877* , replacement: 1877* pref: 70, trunk: toll-free outbound , pattern: 866* , replacement: 866* pref: 75, trunk: toll-free outbound , pattern: 1866* , replacement: 1866* pref: 80, trunk: toll-free outbound , pattern: 855* , replacement: 855* pref: 85, trunk: toll-free outbound , pattern: 1855* , replacement: 1855* Thanks.
  3. I added that regex to a Toll Free trunk with a pref of 81. It's in both pattern and replacement. but it doesn't see, to pick up the pattern because the call goes out the standard outbound trunk. The test call to an 800 number is going out the carrier outbound trunk with a pref of 100 that has pattern of * and replacement of *
  4. Change ^1?(8(00|55|66|77|88)[2-9]\d{6})$ to ^1?(8(00|55|66|77|88)[2-9][0-9]{6})$ ? Thanks
  5. Can someone help me with the correct expression to add to my dialplan? I'm trying to send anything in this regular expression ^1?(8(00|55|66|77|88)[2-9]\d{6})$ out a trunk that I have for outbound toll free. I'm running Version: 57.4 debian Thanks
  6. ahennis, You can set the cdr format on a per domain level and/or the system level. For domain level, as admin select the domain under Domains -> List. Once in the domain, go down to the Advanced -> General Settings menu. This put you in the Domain Settings for Domain xxxxx page. Scroll down the page to CDR Settings and add the CDR format you want to send in the CDR URL field. craig@cdr-reports.com
  7. This is the most recent area I have been using. https://vodia.com/documentation/cdr Hope that helps, craig@cdr-reports.com
  8. chaddow


    You can contact me at craig@cdr-reports.com or through the website www.cdr-reports.com . We are doing a limited rollout now to manage the load. Let me know if you would like a webex demo and we can set one up. Thanks, Craig
  9. Sorry, didn't see your response till now. Trying tshark, I'm getting the Quality metrics truncated in the json format. tcpdump is giving me the full file, so I must be missing something in the command string. Member Key: "Quality" String value [truncated]: VQSessionReport: CallTerm Can you provide the tshark command you are using to get the entire file and I'll run some tests on the vodia sending side and the capture server side. Once I can get the json post completely using tshark, then I can test with the webcdr method. Thanks.
  10. 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
  11. chaddow


    Miguel, Are you still looking for this tool? I have something built that does just a basic call records display, like you mention. Currently: date/time, incoming/outgoing/internal/redirect, to, from, call duration, and domain. I'd be interested in having you try it out and see if it does what you want. We are adding additional features and it would be great to get your input. Thanks, Craig
  12. chaddow

    Understanding CDRs

    Something else to keep in mind related to multiple call legs and forking calls. When a call is forked to multiple outbound cell phone numbers, the customer may not have enough channels available if you are limiting that as part of your product offering. Each outbound redirect will use a channel (trunk). Even if they do not ultimately connect to the outbound device, the channel is in use while attempting the connection.
  • Create New...