Jump to content

AlanS

Members
  • Posts

    66
  • Joined

  • Last visited

Posts posted by AlanS

  1. So, I put my cell as the redirect. Yealink shows "Always forward enabled" but the deskphone still rings. Do I need to include the 1 infront?

    Ok. The button works correctly. Vodia shows the number on Forward all calls to: my cell

    But the yealink still rings. The yealink even shows it on Always forward calls

    Is this because the extension is in a call queue?

  2. I can confirm this is indeed not working correctly. 

    This is what's happening.

    1. Vodia -> add server -> {name, url} -> yealink rps -> returns 400 {server name already in use} //This is where you should have stopped executing your code.  I can't find the POST BODY in the logs, so I don't know what you sent originally. 
    2. Voida -> add device -> {mac, serverName} -> yealink rps -> returns 400 {server name is undefined} //ServerName is undefined, because it was not created in step one.
    3. Repeat 3 more times ha.

    The original error "server name already in use" is strange. I would have to see what name was being sent. This error happened to me too. But, I have a fresh RPS account with nothing in it.

    This isn't that big of a deal for me. I remember a couple of years ago, when yealink was changing and deprecating core urls and functions MONTHLY. At the company I did work for. I created my own autop service with the yealink rps. Boy was it a pain. Every month, was some crazy breaking change. 

    I am just adding the servers manually in the RPS until this is fixed. No biggie. The Grandstream RPS is outdated too. It's not working for the new GDMS. But, again, I just do that part manually. I really don't mind.

     

    Advice to anyone landing here, just create the server and add the device in RPS Management, and then add the mac to the extension in Vodia and don't forget to open it for provision.

  3. On 4/30/2020 at 10:42 AM, almoondsllc said:

    I have a config like in the Screenshot attached but whle I'm listening on 192.168.178.123 port 8181, I'm not getting nothing there when I call the 4000 ivr node from an internal phone and even if I digit something, nothing happen, that's why I asked just an example of the configuration

    Istantanea_2020-04-30_17-39-58.png

    Istantanea_2020-04-30_17-39-27.png

    I noticed {Output} doesn't send anything to the server except '{output}' in string format lol.

    How were you able to send the captured digits?

  4. Is this a planned feature for the future?

    If not, can it be?

    I have a client that doesn't really have an IVR. I created an auto attendant, that just sends all calls to the main call queue during normal business hours service flag. But I want a message played when they first enter the queue (text to speech).

×
×
  • Create New...