Jump to content

Logicwrath

Customers
  • Posts

    578
  • Joined

  • Days Won

    21

Posts posted by Logicwrath

  1. Honestly, we are already setup with Vitelity and for some reason we moved away from it, I can't remember why at this point, but we do have an account with them and did test it out.

    For what it's worth, I recently did quite a bit of testing using 2600's fax2email and email2fax and so far we have had 100% success rate.  I was quite impressed.  We sent faxes to US and Canada with 0 failures.  I don't plan on using ATA's if I can avoid it, but I do want to be ready to try it in those special cases.

    The testing I did previously with this ATA and an Obihai was with my previous carrier VoIP Innovations.
  2. I would like to use the Yealink RPS server to drop ship handsets to my customers.  I enter in the MAC address into their website and it will correctly redirect to the Advanced Provisioner URL and configure the phone.

    The problem is that the Advanced Provisioner does not set the server URL in the Auto Provision settings of the Yealink configuration.  Any changes I make to the devices configuration in the Advanced Priovisioner will not get applied at reboot because it is not configured and not checking-in after the first redirection from Yealink's RPS service.

    It appears that I cannot use this RPS service correctly until the Advanced Provisioner sets that field.

    Thanks!

    Additionally, please also consider adding the Label Length field to the options.  I typically set this to Extended on the T46G otherwise it will cutoff anything longer than about 4 characters.

  3. I have a specific need to automatically change the caller id based on the destination number.  A specific customer has 7 or 8 numbers in multiple area codes and likes to change the caller id based on which area code they are calling.

    I have been creating call flows using postman to try and solve this because patterns and the set_cid module are not available in Monster.

    The problem is that my pattern is not matching/working.  If I create the exact same call flow using numbers, the set_cid module works.  If I switch to patterns, it always chooses the default caller id.

    Here is the JSON I am using to create the call flow:  http://pastebin.com/91QSUnDf

    I have tried 3-4 different patterns.  As soon as I use numbers instead, the call flow functions correctly.  It appears that something else is matching first like no_match.  I assume this because I can see different recording URLs in the call logs.

    If I post the pattern with a * in front like ^\\*(1586\d{7})$ the correct call flow will get matched but the call is sent with the * and fails.

    Can anyone help me understand what I am doing wrong?
×
×
  • Create New...