Jump to content

koolandrew

Members
  • Posts

    159
  • Joined

  • Last visited

Everything posted by koolandrew

  1. 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.
  2. 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
  3. 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
  4. 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!
  5. 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.
  6. I appreciate your reply but we are going around in circles. We have tried the third party log in without success. We have tried the rest api with curl without success. I am not sure how the third example would help us log into the web page. PLease advise if this is possible.
  7. Our intention is to use this code to log in to the pbx web page, not grab a log. Does your solution solve that? Please advise.
  8. Hi, i was wondering if there are any updates. If this doesnt work, so be it.
  9. Yes, and the debugging shows that its not returning any session information.
  10. Thanks, hopefully this will help. vodia66log.txt
  11. i wish it was that simple...no blacklisting...the ip that its coming from is listed in the api
  12. For some reason, i never got this reply. Yes it is a domain on the server, yet no response. If this doesnt work, just let me know so i can move on.
  13. We have tried this on v65 and upgraded to v66, and when we follow the documentation, we get a no-reply from the pbx. Any ideas on how to resolve this, as we added the proper ip from which the api came?
  14. Have you checked with your provider, maybe they are metering your usage, and you have run out of funds. They are so many things that could go wrong on inbound calls, what you need to do to perform a trace. Find out where the calls are failing, by checking the logs on the vodia, and then if they dont provide the answers, find out from your provider.
  15. Ok, this still a little vague...please remember as your status says "Advanced Member", i dont have all your knowledge. When you say "Multicast Paging Group" what do you exactly mean. i am just manually provisioning to get this to work. IThe choices, on a Grandstream, for example are, to add the multicast ip (224.1.1.2:4000) in the multicast paging section and give it a label of page. I go to the vpk section to add a button. I add the description of Page, and value of 224.1.1.2:4000, and select Multicast Paging. I could also select Multicast Listen Address, but i dont believe that is what you are suggesting. It actually worked, with no pbx cdrs as you said, the only difference that the PA1 and the other phones play the message. THE BIGGEST ISSUE REMAINING IS THAT THE MESSAGE IS ALSO PLAYED FROM THE PHONE THAT YOU ARE CALLING FROM, HOW TO PREVENT THAT NUISANCE, AS THE PLAYBACK IS AWFUL
  16. Thanks for the quick reply. All the phones support multicast paging, there is only one PA1 and they are all on the same lan. Are you suggesting, creating a Unicast paging with the PA1 extension only in the group, and using the PA1 to multicast to all the phones that have the multicast ip setup. In this case, the pbx would effectively only unicast to the Snom PA1 and it in turn would multicast to the phones that have been setup?
  17. There isnt alot of information regarding this topic, so hopefully the response will be useful for others as well. Three options No pbx involvement with paging 1. I have gathered that you put the mulitcast ip address from the PA1 and copy it to the mulitcast settings on whatever brand of phone you choose ie (224.1.1.2:4000) so they will ring at the same time as when the shortcut key on the phone is selected with this value. Pbx involvement 2. Call the paging extension (unicast) and put the SNOM PA1 extension number in as one of the extensions to be dialled. It in turn broadcasts through the multicast ip to the other phones that are selected. 3. Call the extension number of the PA1 directly from any phone to start a page and the other phones will broadcast as above. Thanks
  18. When the country code is set back to 1, and that setting of dont rewrite on a trunk is set, the + gets removed when using "dont rewrite" or "use + symbol at the beginning". I dont think there is any way to use the 1 as country code and keep +1555555555 (for example) on inbound calls.
  19. i mean it doesnt work...the number dialled +442070046000 becomes 011 when it is goes to the carrier. In any event, i have unlocked this mystery. The one topic not discussed was the order of the dial plans as the order screwed it up. I had to put in the +1* rule at the top...and voila it worked. Regarding the other one, i figured it out as it is is simply +* and again, it has to stay in that order for it to work. thanks
  20. The first one works...............hooray!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! The second comes out as 011........................
  21. I have tried and all the calls go to the second entry but it never changes as it goes out to the 011(2-9)* to the carrier.
×
×
  • Create New...