Rick Guyton

Thanks for that update @Darren Schreiber! I've been worred sick about there being some issue and my clients getting shut off.

@Darren Schreiber I looked at my account after the update today and I don't show any CC info filled out at all! But, thankfully, my card was charged for services, so I think I'm good. But, I'm not sure if I should update my card and how I can access either of the features we talked about in this thread.

Well, kind of. I get the ID of the device, but that in and of itself doesn't mean anything. Technically, I could call back out to the API and get more data on that device. But, trying to do that in the limited time scope of a call placement... Ugh. I'd have to build a database to have that info on hand. I'm considering doing something like that... But, it's a lot of work and 2600 could do it better with an internal resource. Easy, set that as the caller ID in adv call flows you you've already mentioned. Easy, use the Static Caller ID section of my post. Then you'd assign a star code that ANYONE on the account could use to call out on the second business number. In addition to the main and secondary??? Seems kind of overkill.. But, no pivot doesn't get me enough info to know who the user is at all I don't think. So, same as #1 Yea, again, I'd need more info that what a pivot call gives me. So, same as #1...

Hey Eugine, You can do that now with pivot. Your welcome to steal my script below for this. Think Darren mentioned they are making an official version coming soon. Next up, how to make that same *code use different numbers on different devices. AKA, if I dial *1 ten digit number, have it use MY personal cell number. And if my wife on my same account dials *1 ten digit number, have it call out on HER personal cell number. Finally, setup CallerID prepend, so that incoming calls have a *1 on them if the caller called your personal number. This would result in a pretty sweet config where each user can use *1 (or whatever) to call out on their personal number AND ID inbound calls from their personal number by seeing that *1 AND be able to call back off the call log and have it work as expected (call back that same person using your personal number)

I like that idea as well. But, I'd personally probably still be a bit uneasy because it wouldn't account for potential issues between 2600hz and their processor. I understand this kind of thing is SUPER rare but, when you are talking about shutting down all of our clients... Maybe I'm being overly concerned about it, but that' just scary as hell not having time to react to something.

Yes, that'd be great!

After the billing webinar yesterday, I'm left with a nagging concern. I intend to use the "bill this card directly" feature as the idea of having to pre-pre-pay my account isn't very appealing to me. My concern is though, as I understand it, one attempt will be given and if it doesn't succeed, all of my accounts will be shut off immediately. And that would be catastrophic to our business. On the one hand, I kind of understand it. I mean, if you don't have money on your card, that's your problem for not having that sorted. And if that were the only concern, I'd think, well heavy handed, but fair. But in the past 3 years I've had 4 cards replaced due to fraud. It's terrifying to think that if one of those indents could have lined up just right, it could have the effect of shutting all of my customers down. Not because of anything I personally caused, but because some dude skimmed my card at some point and bought the bar a few rounds in a bar in France (yep, that really happened). And this sets aside a plethora of other issues. Like, what happens if we have an issues like those fiber cuts on June 28th... Man, that was pretty close to the end of the month. What if that affected 2600hz's merchant processor. Or 2600's ability to reach their merchant processor? Or what if the merchant is just down? Or they enable a new cipher unexpectedly? What if VISA/MC/AMEX/DISCOVER, just randomly decided that the charge this month looks fishy and does a security decline until they can get ahold of me and approve it. AMEX is notorious for this. I mean the edge cases are everywhere. Just seems like some small safety net is in order. So, can we please have something a bit safer than that? Some ideas: 1) Give us at least 3 days to respond (in case it happens on a weekend) 2) Allow us to have the balance pulled a few days in advance. AKA, change "bill this card directly" to "Bill this card directly [NumberInputBox] days in advance". That way if someone really wants to live on the edge, they can put 0 in there. But, the rest of us can put maybe 3, 5 or 7 days in there. Thoughts?

Hrm, maybe. I think in that post you are talking about "mobile devices" as in a call forwarding device. I'm talking about the 2600hz MVNO service.

Well CallerID doesn't come through to the cell. I'd considered adding a callerid number prefix. But, even after dis-associating the phone from my user in SmartPBX, I can't create a call flow for my personal number. ADV callflows says there's another callfow with that number already. Tempted to just delete that callflow via API, but not quite sure what that'd do on the 2600hz side...

Hi all! I finally made the leap and put my personal phone onto 2600hz mobile. Anyone know how I might be able to differentiate calls that route in via my office number as opposed to my personal cell number? Previously, I'd had a "cellular device" that simply used the office caller ID. But I can't quite do that...

Yea, probably right. Mis-read the original post I guess. I'm thinking mine is more of an ongoing local issue with Cox. Thought it might be realted

Hey Travis, We've been seeing a lot of this too in AZ. I'm trying not to have a tin foil hat over here. But it started after net neutrality started to get knocked around for us... At the end of the day, we use Queue Trees on our MikroTik routers and I just have to limit down the max throughput on them. On a 25/5 connection I used to set a max of 24/4 throttle to insure we controlled prio. But more and more I have do go down to 23/3. 😕 I'm really hoping some day we'll get a definitive process for trouble shooting call quality issues from 2600... I understand it's a complex issue. But it'd sure be nice to know what they expect us to do on our side before going to them.

Hi Jack, When you drag the user/device over in advanced callflows, you'll see a check box that says "Allow this user/device to call itself". Check that and you should be good.

Unfortunately, right now the answer is you don't. We've heard a few times now that templating in the provisioner is coming soon and this will be how you handle it.

Just saw this in SmartPBX. Made my life much easier changing the main menu back for a church after Easter. Thanks!

The customer specifically requested they be split. So.. yea, can't do that. Wish I could. So, update, the APIs will at least allow me to upload a device with it's ID included. I 1/2 expected it to kick that back. I'm feeling pretty confident now. I'll be deleting the old devices from the old account shortly and the devices seem to be coming online ok... EDIT: So, basically, I had a three questions here... Q1: Will Kazoo allow you to use an ID from one account and PUT it into another? A1: Yes, it allows this. Q2: Even on the same cluster?? A2: Yup. Q3: Will the fact that there's is an identicalobject with an identical ID in another account cause any call routing issues. Obviously, it's not best to keep objects in both accounts long term. But, there is some benefit to being able to fall back to the old account if needed. A3: No, devices/callflows/ect seem to work fine even with an identical object with an identical ID in a different account.

I've got a client that purchased a whole bunch of companies and brought into our phone system. They are now divesting of a bunch of them and so we are having to move these phones/users/VMs/callflows into their own separate account. I'm thinking about simply GETing the JSON objects our of the source account and POSTing them into the new account. Does anyone know if I can simply keep the existing IDs? It'd hugely de-complicate this if I can keep the IDs.

I heard somewhere that if you set up a callflow for the number 0, it will get used when someone passes zero in voicemail. I’ve never had a need to do it myself. So I’m not a hundred percent sure

Yea, you can create the call flows with this doc: https://docs.2600hz.com/qubicle/doc/callflows/cf_qubicle_recipient/ You can't make it with the UI though. You'll need to use CURL or Postman or something.

Yea, I've floated that with my clients and it doesn't go over very well for me at least. They complain about having to constantly watch the portal to see if they've been kicked away.

I think 4.2 is up on the sandbox. I'll go play and see if I can figure something out first. Thanks @mc_

Man, everything I want is always in the next release. Not sure if that's a good or a bad thing. But, yea, that seems a lot more sane a way to address this. I'll wait. Out of curiosity, can you append to existing values? For instance could I have a key "menus" that's set to ":LocationAMainMenuOpt3", and then later append ":LocationBMainMenuOpt4" to that? This way later, I could split on ":" and know the client originally called location A and punched a menu to go to location B and pressed option 4 there as opposed to calling Location B directly and pressing option 4? Or maybe (even better) can I assign a key like "Menu_%Timestamp%"?

Oh, good point, I didn't think about that. That'd make the situation a lot better. But, I'm still curious about those zero length unicode characters though. It'd be nice to be able to track this by looking through CDRs without it popping up on user's phones.

A couple of our client's systems are getting quite large and we are running into an issue. That issue is we frequently can't figure out how a particular call was routed to a particular phone/user/mailbox. To dig further into this we need to put a ticket in with support to have the logs pulled. This works, but it's not optimal. So, I considered putting caller ID prepends into each menu options. But, some of the menus get 3-4 deep and that's just too many prepends, users would have trouble seeing hte actual caller ID. Then it occurred to me, there's a few zero width unicode characters. I could prepend with those... But if I do that, am I going to break anything? Has anyone done this before? I was considering using: U+200B U+200C U+200D U+200E and U+200F

Awesome, thanks for that info @mc_! We have a media file we need to use with our sub-accounts frequently. This will be a great help. We've been uploading and uploading...