Jump to content

FASTDEVICE

Members
  • Posts

    437
  • Joined

  • Days Won

    26

Posts posted by FASTDEVICE

  1. We are having internal discussions regarding providing this version of Harmony for free. There are four requirements to using Harmony;
    1. Setup Webhooks on the account 
    2. Requires a device (softphone SIP connection) per user 
    3. Registration to our license server.
    4. Create a Callflow for the Harmony extension
    Although Harmony requires a SIP connection, it does not have an interface to make or receive calls. The SIP connection is strictly used to process caller ID information. Our future desktop integration, Harmony v2.0 will no longer require a SIP connection, but uses WebSockets and a messaging queue. It will also have extended features and be sold per license.  
  2. Using schema callflows.resources.json, would it be possible to add something like to_sip_url ? This way we can configure:

    From account to account
    {"module":"resources"  ,"data":{    "to_sip_url":"xxx@realm.com"    ,"use_local_resources":true  } }<br id="null"><br id="null">// external (global)<br id="null">{"module":"resources"  ,"data":{    "to_did":"xxx@domain.com"    ,"use_local_resources":false  } }
  3. I looked back on my support tickets for the GXP2160 and found one from March 2015 v1.0.4.16...
    Thanks for reaching out. Arthur suggested we look into Grandstream and to evaluate the GXP2160 as a potential replacement  for our go-to workhorse the Yealink t2xp series that is starting to look aged in the workplace.

    My team conducted interop and quality testing, but the device failed on all accounts. The firmware was not compatible with our SIP proxy from 2600hz.com, the phone buzzed using PoE. and voice quality was scratchy and distorted on the receive side. Perhaps the latter was due to a defective phone, but GrandStream forum users state otherwise.


    They never did resolve the SIP proxy problem and we returned the phones.
  4. Grandstream has many templates on their support site, but according to their tech support team, they suggest to factory reset the phone, configure as needed, then export the config file. This should give you a default working set of parameters in .cfg format. However, you will need .xml to download to the phone.

    That said, they have a bash script (tool found on support site) to convert the config file to proper XML for provisioning. After which, I suggest replacing key parameters with say, "%ext%, %passwd%, %realm%, %proxy%, %prv%, %firmware%" and then use sed/ perl/ php to find and replace them with client information.

    I've broken the config file into two; cfgMAC.xml and cfggxpMODELNUMBER.xml. If you choose to encrypt, you can request a GAPS template that gives you an encryption key option. They recommend using openssl enc -e -aes-256-cbc for encryption.  
  5. A rep from "thinq" gave me a demo of their carrier (LCR) service and it seemed very impressive with a lot of features and granular capability within the feature sets. What caught my eye was Peerless was on their carrier list along with many big names.

    I was wondering if anyone has experience using them? Something like this would be an interesting choice for when Darren reveals his updated billing model.  
  6. @Maire are you making sure the client is using a preferred resolution and scan quality for faxing?

    Here is what I have found works best:

    If you are scanning documents, your scanner software should allow you to set the resolution (measured in DPI or “Dots Per Inch”) of the scanned image. Fine mode fax is 204 x 196 dpi and Standard mode is 204 x 98 dpi, so 200 DPI is adequate for both Fine and Standard resolution faxes.

    We recommend you scan your documents in “black & white” to produce a crisp, high contrast image. The key to getting clean looking faxes from a scanner is to make sure the brightness and contrast settings of your scanning software produce “crisp” images so there is as little grayscale in your image as possible. The text and any line art should be as dark as possible and the whitespace should be completely white and free of any “haze” or grayscale. However, sometimes you will intentionally want detailed grayscale images if you are faxing a detailed photo or image.
  7. My thought is provide direct SIP dialing across accounts. This way we can create a callflow with a devices that points to a SIP address in another account. While not a perfect solution given the caveats, it's one that should exist.
  8. @Darren, I'm running into an interesting issue with SMS providers and the choice of underlying carrier that 2600hz assigns. The most predominant landline DID enabling SMS service is Zipwhip and they are rejecting anyone using Bandwidth.com. It's not Zipwhip per say, but Bandwidth that is causing the problem. Whenever Zipwhip converts a landline DID to their service, within weeks Bandwidth reverts the SMS service back to them. Therefore, Zipwhip has given up and refuses to enable anyone on Bandwidth for obvious reasons. 

    In fact, if Bandwidth doesn't change their policy, I'm inclined to ask not to use them going forward.  I believe it's small things like this where the option to select the carrier makes sense.
×
×
  • Create New...