Jump to content
Vodia PBX forum

All Activity

This stream auto-updates     

  1. Today
  2. Can I upgrade the Zeta Perseids version to a standard 62 version and have a trial period to see if it works. I see that the standard version has a 3-month trial period, giving me the time to check out if everything is working ...
  3. Yesterday
  4. Without really looking into the details (this is a pretty old version) the problem will be that the door phone sends a SDP with multiple m-lines, which probably confuses the PBX. What you can try here is to disable the video function on the door phone or make a backup and try and upgrade to version 62 to see if it works there without problems.
  5. Vodia PBX

    Caller ID update on trunk

    There is some documentation at https://doc.vodia.com/trunk_ani on how the PBX determines the caller-ID. However many carries don't allow caller-ID that are no owned by the PBX on their trunks, which is understandable considering the problems with SPAM calls.
  6. Voip-Vet

    Caller ID update on trunk

    You are right about the From/To headers. The more down-to-earth problem I'm having is that I can't find a way to carry the From or Identity header of the incoming call to the outgoing call when the pbx is transferring the call out to another number. I don't know if you see possibilities there. Marc
  7. Vodia PBX

    Caller ID update on trunk

    The From/To headers have become useless - the remote party is usually indicated in the P-Asserted-Identity header. We are not aware about one single way to address this with all SIP trunk providers, it seems that everybody has a slightly different opinion about it. It would be great what provider you are using and how they want it.
  8. Vodia PBX

    FreshBook Integration

    You also have to keep in mind that Freshbooks came up with a API V2 - which is totally different from API V1. If you recently signed up you'll need the V2 support. That was no available when 5.2.5 was made.
  9. Last week
  10. Voip-Vet

    Caller ID update on trunk

    I got stuck on the fact, that the original FROM Header is replaced by the pbx when it starts the new call to route the incoming call. I don't find a possibility to 'keep' the original FROM. I was hoping that the Trunk 'Update Caller Id' did something like that, but obviously it is not. So if anyone can think of a way to transport the FROM from the incoming call to the FROM of the outgoing call, it will be very easy to pass on that information to the trunk.
  11. Support

    FreshBook Integration

    In that case, it might actually be a bug and hence 5.2.5 was introduced to fix it. So on and so forth. You can always upgrade, as developers won't be working on that build anymore.
  12. Pbxnsip Zeta Perseids / Grandstream GDS3710 Video Door System Problem : when DoorStation makes a call to the pbx and an extension takes that call, there is only audio from the doorstation to the Extension, not the other way around. When I make a direct IP┬Ęconnection from the doorstation to one of the phones, all is well. Sip log of a call in addendum : could anyone look into this to check what might be wrong ? Any ideas very much appreciated ! Many Thanks, Marc Pbxnsip Grandstream Doorphone Sip Log.txt
  13. Rameshkumar

    FreshBook Integration

    That works. Also in 5.3.2 version I think there is a bug, In monthly billing if I put the email and run the test it's not generating email. Though I've 5.2.5 version and it works fine. Please advise.
  14. Support

    FreshBook Integration

    Hi, Try this: https://portal.vodia.com/en/freshbooks
  15. Rameshkumar

    FreshBook Integration

    Hi, I'm using Vodia 5.3.2 version and I want to integrate it with freshbook. I was reading the doc https://doc.vodia.com/billing and I found I need to generate a token to authenticate PBX with Freshbook. When I click here https://vodia.com/en/freshbooks to generate token it says page not found. Please allow how can I integrate PBX with freshbook? Thank You
  16. chrispopp

    Caller ID update on trunk

    I am also interested in the same setup. Did you figure it out? Trying to use something like this, but it doesn't work: {from-extension}{ext-ani}{from-trunk}{rpi}
  17. Support

    Snom phones incorrectly provisions two identities

    The latest release is of 62.0 version.
  18. Vodia PBX

    Snom phones incorrectly provisions two identities

    This should be fixed in the latest version so an upgrade would also solve the issue.
  19. Vodia PBX

    Provision logo on Yealink phones

    The idea about the logo is that this a a company logo - usually easily presentable as a vector with colors. The problem is that most VoIP phones today take a very technical view on it and provide a mechanism to upload a wall paper which on some phones stays there even if there is a call going on. This is not the same thing. We are now provisioning well over 100 different models that have color displays. It is not very easy to keep up with new displays and user interfaces - it would be great if new VoIP phone firmware would be able to pull a PNG or SVG image and handle the logo display locally and properly.
  20. Vodia PBX

    New licence plans / No info on website

    Sorry about that confusion. 888VoIP is a US distribution company. We highly recommend them if you are purchasing in the USA. For other countries everything stays the same. The portal for vodia is still available for you 24/7.
  21. Support

    Provision logo on Yealink phones

    If you want to do it for a group of phones, then you will have to do it separately on the extension level of each phone. "Group" as such isn't defined on the PBX.
  22. koolandrew

    Provision logo on Yealink phones

    Ok, i think im starting to get it. I thought maybe there was a way of selecting a group of phones, that would have different provisioning parameters. Thanks again for your input!!
  23. Vernon

    Snom phones incorrectly provisions two identities

    For those looking for a possible work-around for the time being is to copy/paste the phone-MAC.xml file from the generated folder into the extensions custom phone xml. e.g snom_745_phone.xml...etc It seems like the first extension in the list gets the settings for both extensions, while the second identity phone-MAC.xml only generates for itself. It may not be pretty if it's for the whole system, but for individual extensions it should work well enough.
  24. Support

    Provision logo on Yealink phones

    Hi, 1. It can be either, as long as it's resolvable and enabled for your phone to reach. 2. Look for "Customize" section on Extension, Domain and Admin level. We have shared a screenshot from the extension level.
  25. koolandrew

    Provision logo on Yealink phones

    Thanks for the reply so quick. 1. Is the http url the domain or public ip address? 2. Is there a way of changing this and other settings to only specific phone ( or extensions) according to requirements of the locations in the domain. Thx
  26. Support

    Provision logo on Yealink phones

    Hi, Not sure about the 22 and 28P model but we do have the entry for 29G model and it should be in this format: #Configure wallpaper {if_model T29G T46G T38G T32G} wallpaper_upload.url = {http-url}/logo-480x272.jpg phone_setting.backgrounds = Config:logo-480x272.jpg {fi_model} So please keep it in this format and remove .dob file settings from there and it should work as it currently works on our T58 model sitting on our desk.
  27. We realize that you are very proud to be represented by www.888voip.com as a sales agent. But for us it's a step backwards. At least at this point. We used to buy annual maintenance through your website. Now we have to browse through 53 unorganized items on the 888voip website trying to find out which is the replacement for our original maintenance contract. www.vodia.com has no licence infrmation page left at all (at least we were not able to find it). Does your marketing team intend to scare the smaller clients away? We understand that hiring a reseller makes a lot of sense from a business point of view, but you probably would't want to confuse your clients because there is no straightforeward information. So what do we have to buy as a replacement for annual maintenance. We weren't able to figure this out quickly.
  28. koolandrew

    Provision logo on Yealink phones

    Thanks for quick reply and suggestion about upgrading, which needs to be done. Although i need to test caller id as i received other posts where people have concerns about this since the upgrade. In the mean time, this is what i did to change the file: #Configure the logo mode of the LCD screen; 0-Disabled (default), 1-System logo, 2-Custom logo; phone_setting.lcd_logo.mode = 2 #Configure wallpaper #http://192.168.1.100/wallpaper.jpg #wallpaper_upload.url = http://192.168.203.183/rest/domain/localhost/image/logo/480x272 wallpaper_upload.url = http://pbx-public-ip/Logos/t22p_logo.dob #wallpaper_upload.url = {https-url rest}/domain/{domain}/image/logo/480x272.jpg phone_setting.backgrounds = Config:480x272.jpg My questions remain, we have three phone models, old T22P and T28P, and a new T29G, which is colour. How do i set it up to load 3 different sizes and one with colour. Do i still need a .dob file, as per the Yealink website How do i set this up for some phones in the domain, as some phones will be loaded with these changes and some wont, according to their location preferences. I hope these questions arent rudimentary but we have always used our own system for provisioning but would like to start using Vodia. Thanks
  1. Load more activity


  • Who's Online (See full list)

    There are no registered users currently online

×