Jump to content

FASTDEVICE

Members
  • Posts

    437
  • Joined

  • Days Won

    26

Posts posted by FASTDEVICE

  1. I'm using the branding app and would like to know how to properly configure the "Realm Suffix."

    My understanding has been, from prior branding, that it is preferred to have the realms created in this format: *s.yourdomain.xxx" The DNS helper even shows the MX and proxy fallback in that format. However, if you configure "s.yourdomain.xxx" as the Realm Suffix, the DNS helper shows the format as: *.s.s.yourdomain.xxx"  and all the A and CNAME records get an 's' inserted as well.

    I ask what is correct, s.yourdomain.xxx or yourdomain.com for the Realm Suffix? 
  2. @Darren, interesting reply as my developers are telling me that an email account is now required to create a user. We have been using "account_ext@fastdevice.net" as the username to create the user's account. However, the email account for sending vm and fax is separate. We also don't expect these types of users to be logging into the monster portal. Is there any issue (besides logging in) with making a bogus email account name for the username? 
  3. @Darren - perhaps this needs to be incorporated as part of a callflow element(s) (those that answer/ listen). I don't think most people on this board are going to write the callflow JSON necessary to configure the two child callflows for fax or voice.  
  4. Darren, on a side note...at some point your business model is to support 3rd party applications through an apps store of sorts. Where can resellers that develop these apps or layered services that extend 2600hz offerings appropriately begin discussions? I'd like to get feedback on what my team is building and perhaps have the community drive some of the direction.  
  5. My development team has already build desktop integration that hooks to Web and Window's apps to pop contact information screens for CRMs or launch applications. This has been deployed for about 1.5 years and working flawlessly. This month we are deploying a full admin/ user portal with call analytics that provides reporting on extensions and phone numbers.  
  6. There is an alternative way that doesn't need to traverse the cloud  and responds instantly. In many brand IP Phones, (Yealink my favorite) there is a config section for Multicast Listening. In that section, there is usually 10 groups that you can assign.

    My preference is to assign:
    224.0.1.116:5001 as Page 1
    239.255.255.255:1008 as Page 2

    Then, program a DSS key as type "Multicast Paging" with one of the IP page addresses as the value. 

     
  7. Darren, I'm thinking it's not an edge case for me. A number of prospects and current clients have multiple businesses under one roof with a central admin answering calls and routing. I'd like to keep the businesses separate and in this case don't need extensions calling one another, but need the admin to route the calls to their extensions. And, I need the system to grow with this "rental" business model beyond the capacity of a multi-account SIP phone. However, I have multi-locations as the dominate request.
×
×
  • Create New...