Jump to content

koolandrew

Members
  • Posts

    178
  • Joined

  • Last visited

Everything posted by koolandrew

  1. Please look at the link https://doc.vodia.com/docs/autoattendants, there is a hyper link that refers to "nested within one another" and it links to https://doc.vodia.com/docs/autoattendants-nested. However it is 404 not found. Is it possible to have more than the allotted shortcuts. I know it is possible; however, if a caller is listening to the greeting, and they hear the options from 1-9 (for example) on the first IVR, and then it rolls over to IVR 2 for 10-13 (for example) and they dial 3, they will hear that it does not exist or something. Similarly, if they call back, and press 11 during the first ivr, the call will not connect. Is there a way to resolve this issue. Please advise.
  2. Is the procedure for 69.0.x the same as previously to recover lost password, or is that possible any longer with the keys element? Please advise.
  3. i appreciate the reply but i am not sure we are any closer to the answer of my original query. I hope my reply will generate a response, as i appreciate someone responding. So when a user in the US receives a call, it should show as 011-44-xxx, while the same call would show for the UK caller as 00-1-xxx (probably 001-xxx).--i know this isnt the case. When a UK cell phone user receives a call from the UK, it is 0 followed by the local number. Not sure about the +. it should show as 011-44-xxx,--this is the vodia pbx that does this, i dont know why it isnt +44 then the country code, but this is hard coded to the voida That is perfectly okay. In order to make it easier to write dial plans, there is a setting in the dial plan of the PBX how it should present the number to the pattern matcher, and again, if you don't like the default, you can explicitly say there how it should be presented. I am not aware of a setting for the dial plan to change this, as i was under the assumption that the dial plan was for outbound calling as it has to match a trunk. it should present the number to the pattern matcher. i dont know what this means, as i have not been able to figure that out. The questions in the post from February 9th remain unclear. Thanks
  4. HI,Thanks for the reply, i was hoping to get one. i understand that + is accepted, as that is what we are trying to do. I am trying to interpret your reply based upon my previous questions below. Our provider presents the call correctly, it is Vodia that adds in automatically all this 011 stuff as it is set up as a North American pbx: If it is a us based phone systemand all the calls come from one ip x.x.x.x for example, , and we have trunk A for us calls, and trunk B for Germany calls and trunk C for UK calls, would the system route calls to those trunks and know to send calls to the specific inbound trunk--so your answer is yes, ok with those calls and know that for calls coming from the UK to strip the 01144 before the number and change it to 0 before the local number.---can we do that as your reply doesnt address it? Similarily, would it present a call from Germany, for example, to the UK in the appropriate format as it would from the USA.---what would happen in this case or can we make rules for it, as i cannot find any documentation on such. The Europeans dont know anything about 011 so it would preferable to rid that from their calls, and it more importantly, if they are getting calls from within country to an inbound DID that the caller id is local.
  5. This is quite fuzzy for me, as there is documentation, but it is not clear on the handling of inbound vs outbound calls. I am not clear on what to do if the same trunk ip address is used for inbound numbers from multiple countries. If it is a us based phone systemand all the calls come from one ip x.x.x.x for example, , and we have trunk A for us calls, and trunk B for Germany calls and trunk C for UK calls, would the system route calls to those trunks and know to send calls to the specific inbound trunk with those calls and know that for calls coming form the UK to strip the 01144 before the number and change it to 0 before the local number. Similarily, would it present a call from Germany, for example, to the UK in the appropriate format as it would from the USA. The Europeans dont know anything about 011 so it would preferable to rid that from their calls, and it more importantly, if they are getting calls from within country to an inbound DID that the caller id is local. Hopefully, this is clear.
  6. Is there a way of presenting a local calling number in a pbx where there users in several locations. For example, in the UK, they would like to see the number presented as 0XXXXXXX vs 01144XXX or 44xxxxxx when someone calls, as they would on their mobile phones. They also have locations in the USA and those calls are fine. Please advise.
  7. I would suggest reading the docs, as i am not even sure how to answer that question. Everything depends on your extension/trunk and if appropriate inbound trunk settings.
  8. Please point me to the template page, there is no makecall.htm, is it listed under another name. I am not sure on this hack, as you would already have to be connected to inspect the browser..i guess you can override the file on the vodia pbx, is that the "hack" that you are referring to? thx
  9. I am just following up on this page, is there a way to edit makecall.htm file. I dont understand this response as this file is on the vodia server, but it is not a customizable template. Am i missing something here. Thanks
  10. Regarding this topic, it begs more questions unfortunately. 1. How can we place a + in front of the caller id whilst using the 1 as the domain country code. When using that setting for Global numbers it puts the + in front of the dialled number as well 2. Regarding the link for Trunk Custom Headers, there is a reference to Caller-ID fields For the fields from, to, ppi, pai and rpi the system generates the following content (xx will be replaced with the actual field name): For example, {ext-ani-no clip} a valid example? 3. Is this a valid string for Regular ANI rule as it is not mentioned. from-ext:ext-ani !clip:!from-trunk:ext-ani !clip:!from-trunk:trunk-ani !clip:!disa:from !clip:ext-ani !clip:!disa:from !clip:trunk-ani 4. We have tried using {ext-ani-raw} but it doesnt work as there is no caller id presented, as according to the instructions, and doesnt add a + to the caller id. There is no way to add the + sign to the caller id on the extension or trunk as it changes it to 011 which is not acceptable for the carriers. Please advise.
  11. thanks for the quick response. For anything else reviewing this post, the actual opt out message is separate, it is the next one in the list, bi_recording3. Thanks again.
  12. Could someone please tell me the filename for this audio file, as it is automatically played for recorded calls. We need to be able to edit the file as there is no need to give the caller a choice. Thanks
  13. As mentioned in the previous post, it is for both. Posted Thursday at 02:39 PM Thanks for replying, unfortunately that answer creates more questions so here we go, as what you are mentioning is probably fairly common, except the part where the Mexican, UK and USA numbers come from the same provider???????????? and or sent to the same provider?? I believe that is much more common that having a local trunk in the varying locales. 1. How do we separate inbound trunks in that situation as both calls are being received from the same provide/ip address etc but they have to be treated differently otherwise only one of them will work. i) Using the Rewriting global numbers designation, international calls have to be treated using the selection "e.164 without the leading plus" and for 10 digit north american dids you would need to "Use + symbol at the beginning" for international and north american dids respectively. 2. For outbound, how can we display e.164 for the caller id for a trunk that needs a Company Name and +44123456789 (for example) when the country code is for the tenant is set to 1? As far as we can tell, the best you can do is send 01144123456789 (for example) as the "Number Presentation" that you are referring to above, are for the dialled number, not the caller id presentation. Again if this is not possible to resolve, so be it. Vodia has a lot of great features.
  14. Thanks for replying, unfortunately that answer creates more questions so here we go, as what you are mentioning is probably fairly common, except the part where the Mexican, UK and USA numbers come from the same provider???????????? and or sent to the same provider?? I believe that is much more common that having a local trunk in the varying locales. 1. How do we separate inbound trunks in that situation as both calls are being received from the same provide/ip address etc but they have to be treated differently otherwise only one of them will work. i) Using the Rewriting global numbers designation, international calls have to be treated using the selection "e.164 without the leading plus" and for 10 digit north american dids you would need to "Use + symbol at the beginning" for international and north american dids respectively. 2. For outbound, how can we display e.164 for the caller id for a trunk that needs a Company Name and +44123456789 (for example) when the country code is for the tenant is set to 1? As far as we can tell, the best you can do is send 01144123456789 (for example) as the "Number Presentation" that you are referring to above, are for the dialled number, not the caller id presentation. Again if this is not possible to resolve, so be it. Vodia has a lot of great features.
  15. If this is not possible, please advise. Thanks
  16. There doesnt seem to be any reference materials on "Rewrite Global Numbers" under Number/Call Identification for a trunk. could you please provide the correct slection for the following scenario. A tenant/domain that has the following and is using 1 as the default country code 1. Ten digit North American DIDS 2. International dids (it defaults to 011 -country code then number) It appears that there is not one trunk setting that would work for both types of numbers. Please advise.
  17. Here is your post. https://blog.vodia.com/managing-voicemail
  18. As mentioned it was in the web interface as per your documentation posted on the web. It was a menu item under extensions, long removed but supposed added back? I wasnt asking whether a phone supported it as most do. Was it added back at some point?
  19. Was this feature ever added back in as i dont believe it was. Please advise.
  20. Dont worry about it, i dont want to waste your time. I will figure out another way to work around this feature. You do alot of great work, and i forgot that no one else seems to be using this, so there are much more important things to spend your time on.
  21. We are trying to user third party login, and it doesnt work. Can i provide you a test user:pass and you could try with your code to see if it works. Please advise
  22. HI, i see that you updated your documentation on this topic for Third Party Login, but we have the same results as it doesnt work. https://doc.vodia.com/docs/thirdparty Is there anything that is missing from this API as it doesnt seem functional. thanks
  23. Please understand, if this is any trouble don't worry about it. I am sure this isn't a oft used feature, as no one else has mentioned it on the forums. That is why i used the topic header, and there was nothing in the forums on the third party login, but a fair bit of activity with the php api. I realize that browser security it becoming more and more challenging, so this probably did work at the latest browser updates may have killed it. In any event, if you can resolve it or not, the Vodia pbx is a fantastic product. Keep it up!
  24. Your request (5284) has been received and is being reviewed by our support staff. I am not sure if this was the right place to open up a ticket. and if not i would be happy to do it elsewhere. I never got a reply.
×
×
  • Create New...