jawaid

I have a system in place that logs CDR's from a vodia PBX for incoming and outbound calls - I use it mainly for monthly billing and call usage reports to email to my customers. Please feel free to get in touch to discuss

Thanks will give that a try.

Just wanted some advice or perhaps a better method of doing this: 1 have a customer who wants 2 extensions to ring at the same time, but if no one answers or are busy then he wants a message to be played and the call disconnected. The way I have currently set this up is for the calls to come into a Ring Group and both extensions are in Stage 1. The Final Stage I have to go to an Auto Attendant, where a message is played, however after the message finishes the call disconnects after 20 seconds. IS there a way to either reduce this time or to disconnect the call after the message has been played. I did suggest to give the user an option to leave voicemail message, but he does not want to do that. Any Advice much Appreciated.

I completely agree

Thanks for the advise. I am going to try and get them to purchase newer phones, as I know the ones that work, and can support them better. If they are adamant about using these, going to try and get a sample one to play with first, in which case I will be in touch for advise/assistance.

Hi, I have a potential customer who is currently using the IPECS LIP-9020 SIP phones, wondered if anyone has used these with Vodia? I do not see these on the compatibility list. He has 10 of these and replacing them would probably make him go elsewhere. There is an option of other in VOIP phones, not sure if that would work and whether I could program the relevant buttons. Any advise much appreciated.

I have tried the various methods, and found the 'file' method to be the best, as if the call accounting/cdr server goes down, then I can still get the CDR when it comes back up, ensuring that I do not lose any data for charging customers for outbound calls. With the other methods this is not possible as the data is not stored locally. Unless the other methods could store to a local folder, I can then ftp/sftp the records to my accounting server. I don't require anything more complicated, just the fact that when a call is transferred a record is sent for that leg, so that the call can be attributed to the correct extension.

Hi, I have tested v68.0.14 and the ivr_ext field is now being properly populated with the extension number. Thanks. My only slight issue now, is that if an inbound call is answered on extension A, then transferred to Extension B, the filet method, only gives the cdr for the last person who dealt with the call, rather than a cdr for the call to Extension A as well as a cdr for Extension B. I have test the same transfer for an outbound call and just get the single cdr. Any ideas if there is a way of getting a cdr, per leg of the call using the 'file' cdr option? My cdr reporting solution can log these calls and I can report on inbound/outbound calls, however I cannot provide an accurate report when calls are transferred between extensions.

Thanks That seems to be a good idea. what would you suggest the domain name to use. I was thinking if the area code is 0161 (I am based in the UK), for Manchester use some thinking like residential_0161.domain.co.uk for the domain/tenant name or even residential.manchester.domain.co.uk

Thank you - that is useful to know. I will probably setup different dial/call plans for each number, so that they can dial a local number by just entering 6 or 7 digits, and then translate to the full number..

I am setting up a single domain for residential customers, just wondered what would be the best way of assigning extension numbers. Do I just use an arbitrary 4 digit range, or is it best to use the full E164 Number? Your thoughts, advise and experience please.

Thanks. If you could let me know when the release is available, and I will carry out some more testing.

I will wait for the next build before doing some more testing. Could you not in the next build add the $(ivr_ext) to the file format?

I have already tried the cdr option, the only issue with that is if the call logging server goes down, or connection stops then the cdr's are lost. Unless there is a way of catching up the missing cdr's, I think the only suitable format is file.

I set up a test server with Vodia v68.0.12 and upgraded from CentOS to AlmaLinux without any issues. Test calls have been made with no issues, emailing is working. So looking good so far. @stefanWhat made you choose Rocky Linux over AlmaLinux?

Here are examples of an outbound and inbound call: domain,primary_cid,call_id,from,to,dir,type,start,connect,end,trunk,local,remote,recloc,cmc,ipadr,cqdr,ivr_ext,ivr_user pbx.domain.co.uk,98021128623c1a633e-30042158,daf20cc5@pbx,Jawaid (3501),07768 114xxx,O,extcall,20220324071341,20220324071344,20220324071351,Outbound Trunk,3501,+447768114xxx,recordings/pbx.domain.co.uk/3501/20220324-071344-o-3501.wav,,udp:51.68.195.71:5060,,1,1 pbx.domain.co.uk,614c40702d66f6017a6ee5ba5d3b8a2b@51.68.195.71:5060,614c40702d66f6017a6ee5ba5d3b8a2b@51.xx.xxx.xx:5060,07768 114xxx,Jawaid (44128257xxxx),I,attendant,20220324071434,20220324071437,20220324071445,Inbound Trunk,"Jawaid" <sip:44128257xxxx@pbx.pathwaytelecom.co.uk>,"07768 114xxx" <sip:+447768114xxx@pbx.domain.co.uk>,,,udp:51.xx.xxx.xx:5060,,1, I have changed some of the values to make the calls anonymous, but the important information is still shown. The first call is an outbound call and the local field is correctly showing the extension 3501. The second call is an inbound call is an inbound call from my mobile number (starting with 07768) which is ringing the extension 3501 directly, not via any ivr/ring groups.. The local field in this case is showing my name with the sip address rather than the local extension number answering the call. Even if it showed my name and extension number, I could extract the number from it. Hope this helps. Once this is hopefully working, I will then try calls via auto attendant/ivr/ring groups.

Yes. When you use any of file, filet, fileto, fileti options, there seems to be a standard format for it. These are the fields that are given: domain,primary_cid,call_id,from,to,dir,type,start,connect,end,trunk,local,remote,recloc,cmc,ipadr,cqdr,ivr_ext,ivr_user on an outbound call the local and remote fields show the correct data - in local is the extension number making the call, the remote is the number dialled. but for an inbound call the local field shows the name attached to the extension number and the sip address, the remote field shows the number and sip address of the person ringing in. I made a test call from my mobile directly to an extension via the DDI number, and local shows my name and the sip address, in the remote shows my mobile bumber and sip address. However the call type is showing as attendant. Not sure this is relevant, but there are no IVR, ring groups setup for the DDI number. This is just set against the extension. I would have expected this type of call to just be something like incall.

I am in the process of setting up a test server, so will let you know how it goes. Also going to test migration to AlmaLinux/Rocky Linux as they seem to be the most popular successors to CentOS

I guess that is fine for new servers/systems, but if you have a large multi-tenant system, its not going to be easy to migrate to Debian. What are your thoughts on the new forks such as AlmaLinux and Rocky Linux, Oracle Linux to name a few, as they are RHEL based like CentOS.

I have configured and use File CDR for outbound call billing, and that is working a treat. I would now like to take the next step and log inbound calls, but looking at the output, there does not seem to be a column/field that shows the extension number of the person who actually answered the call. (Even logged in as admin into the admin web portal, and viewing Call Log, does not show the actual extension which took a call). I do get the DDI number that the call came in on, but that does not help when a calls comes into the IVR/queue and gets answered by a single extension. Is there something I am missing on the config side, or has it not been included in this format. Is there anything I can change to get this? The reason why I am using 'file' format, is that I had initially tried using CDR and JSON options, but when my logging server was either rebooted or the services shutdown, the data was lost. So using file method, the cdr is stored locally on the Vodia PBX, and then I just use sftp to download the files to my cdr server. Usually the CDR server will always be on, but I always like to test the worst case scenario.

I am on version v68.0.12 and the issue is still there, here are my findings: 1. We trying to send fax internally (Extension to Extension) nothing happens. 2. When sent to DDI number attached to the extension, the fax seems to go and a FAX send report is received in my admin account (correct attachment included), but no email is sent to the email address attached to the FAX extension. 3. Receiving a FAX from an external number is received fine and sent to the correct email address.

As it has been a few months now, since the EOL of CENTOS 8, just wondered what people are migrating to and why? And following the migration did they encounter any issues with Vodia?

Hi, Just wondering if you have had any feedback on this? I have version 68.0.10 and have the same issue.

That's great. Thanks I shall upgrade my test system to that and check everything.

That means that the issue has been fixed in v68.x as on my test v68.0.7.beta it all works fine, and the settings are exactly the same. Just waiting for a stable release of v68.0.7 or later, before upgrading the customer system. Do you know how long it will be before the release?