Karl Stallknecht

I noticed that the custom ones they list in Adv Callflows under Faxboxes don't actually seem unique after all. The MX records all point back to fax.zswitch.net. I'm stumped...

Has this been fixed?

Can we get an official answer about this? We now have a customer that has multiple fax boxes and the same employees need to be able to send from multiple fax boxes.

Yes, me too!!!

Still isn't working :-(

No, from our sub-account we are dialing a DID in a customer's sub-account.

We are calling from one sub account to another sub account

Just to clarify: - We call a customer from our account to their account - The customer has default hold music set, we have custom hold music set - The customer puts us on hold, and we hear our own hold music I confirmed that this happened on Wednesday (Dec 14th)

This has always been the case for us - if we call a client we hear our own hold music (not theirs), and vice versa.

Ohh okay gotcha! Thanks!

Please don't limit searches to 24 hour periods :-( We get a lot of clients that say "hey someone called me in the last 2 weeks and I can't find their phone number" or "can you pull all call recordings with xxx-xxx-xxxx in the last 2 weeks?" and if the search is limited to 24 hours it's really annoying to try and search the CDRs :-(

Can this be fixed?

Uh oh, this is really important to us too! Are you noticing that accounts you used to set to 3600 are now going back to the default, or you just can't change newly created call recording objects?

I *believe* it's figuring out based off of the user, so yes, this would be problematic if you had a customer that had multiple fax boxes assigned to the same user...in our situation we don't have any clients with more than one fax box (at least that they use for outgoing) so it's never come up.

FYI this isn't necessary anymore :-) All you have to do is send the email with the fax to the SIP realm for the account. Just setup an MX record with your DNS provider to point to fax.zswitch.net and you're set!

Production

So it looks like the failover was added? But it's listed under the number manager? I'm confused on how exactly this works...

I guess I don't really see a way that this could practically work, that's the thing...right now we just contact customers manually when we receive loss of registration email(s) for them. Sometimes they want us to forward and sometimes they don't want us to depending on the time of day, who is working, what else is going on, etc. Basically what I am saying is that I personally don't think it is worth spending time/money building this feature if it would be impractical. I see a lot of people jumping on board with it at first, and then realizing it's not as simple as it sounds and there are too many caveats. But this is just my opinion :-)

@Darren: Let's say the customer's Internet is going in and out constantly one day. This feature you mentioned would cause some calls to still go to their desk phones which might be a bad idea because the call could cut out or have poor quality. So this means that the customer would have to manually enable call forwarding always (or the "* Forward all calls" option you listed above as the proposed setting) in order to make everything go to their cell phone. The phone(s) could signal a loss of registration for many reasons, and sometimes we even see customers have loss of registration emails get triggered but no noticeable outage took place, so this would unnecessarily send a call here and there to the cell phone.

Agreed Rick.  My other concern here is a lot of our customers with crappy Internet lose registration constantly, so this would cause incoming calls to keep going back and forth between their desk phone and cell phone constantly and it would get annoying for the customer.

Thanks

Whoops, I guess we made a slight oversight. It actually looks like some of our phones that were provisioned a long time ago using Kazoo are still pointing to 184.x.x.174 manually (non-DNS). Is there a way to push an update out? We really don't have time between now and December 2nd to finish switching everyone over to Monster/advanced provisioner.

Thanks!

Are the IPs going out of service that you listed in your email all proxy IPs? I noticed we had 209.x.x.233 and 184.x.x.174 listed in some DNS records of ours related to SIP proxies/what our SIP realms are pointed to, so we replaced them with 166.x.x.67 and 8.x.x.3, respectively. Just wanted to make sure this was okay to do. **FYI 209.x.x.233 is still listed in Monster under DNS Helper as the "general proxy fallback" but you said in your email that this IP is going bye bye...is this a mistake on the email or does it need to be removed from Monster? I know you don't want us sharing the IPs publicly, so I intentionally was vague. Let me know if you want us to directly email you with the exact IPs.

The default password pulled from the provisioner is 2600. You can change this in advanced provisioner provider settings.