Karl Anderson

Yup sorry about that, like I say this is the first report but clearly a button that can unexpected change the routing needs to be addressed and we will. The technical specifics are going to take a bit to work out so I do ask for some patience on that. For system admins that have access to the SmartPBX callflows you can remove the 0 (the extension assignment not the callflow) and it will not be added back as long as you avoid the Main Number tab in SmartPBX. However, if you do not and attempt to create it in advanced callflows but have a conflict file a support ticket and we will take care of it until this is corrected.

Sorry, slight correction. The application team tells me that to properly paint the Main Number tab of SmartPBX it is critical that the callflows exist, so clicking that tab creates them. That would explain it because it would add the 0 extension assignment prior to the main number assignment. However, they assure me that it only happens if you click on the Main Number tab. Additionally, they state that refactoring to avoid creating the callflows when loading that tab would be a big change. As a compromise I have asked that they look into ways to create the callflows but without the 0 assignment until the assignment of a main number. I will let you know when we determine if that is viable and where it falls on the road map.

Hmm, interesting I will confirm that with the applications team and get back to you. Maybe they needed to deviate from the initial design to address some issue.

Howdy all, Sorry as you might imagine got busy yesterday and couldn't look into this. Also Tuly if you have a way to share your account name with me (or a support ticket) I can look in more detail. To be clear the 0 extension is not created by SmartPBX until a main number is assigned to the account in SmartPBX and as FastDevice pointed out it should not hijack it if it already exists. Simply viewing CDRs does not trigger callflow creation so wouldn't have any impact here. What I am unsure of is how you are getting to a menu. If you are not familiar with the six standard steps of debugging: That can’t happen. That doesn’t happen on my machine. That shouldn’t happen. Why does that happen? Oh, I see. How did that ever work? We are on step 1, without explicitly creating the 0 extension there would be no instructions that Kazoo callflows could execute to link to a menu. If it was created via SmartPBX then it would be linked to the main number (unless there is a bug) so the main number would play the same prompt. Until I can see an example account's callflows or the logs of a call I don't have any suggestions

Howdy, So Kazoo has no "built" in callflows, so it is finding a match for 0 which sounds like a menu. Perhaps its something that was setup unintentionally? Also, to handle the 0 exit in voicemail and elsewhere SmartPBX will automatically assign it to the main number. If you pull the logs for the call and grep for 'cf_' then you would see which callflow ID is assigned to 0: grep <CALL-ID> /var/log/kazoo/kazoo.log | grep cf_ Feel free to paste them here if you would like assistance!

Howdy, We are still documenting this new functionality, and you should plan on deploying this in Kazoo 4.1 as that is the first version we consider it stable. To get you started there is a new object that you can place on the account, user or device called 'call_recording'. Setting the appropriate values will trigger call recording and store it in the database or the provided URL. Using the storage plans you can have these recordings pushed external to the main bigcouch cluster. The parameter schema is available here: https://github.com/2600hz/kazoo/blob/master/applications/crossbar/priv/couchdb/schemas/call_recording.json https://github.com/2600hz/kazoo/blob/master/applications/crossbar/priv/couchdb/schemas/call_recording.parameters.json https://github.com/2600hz/kazoo/blob/master/applications/crossbar/priv/couchdb/schemas/call_recording.source.json Here is an example payload for the account (the same object could be applied to a user or device): { "data":{ "name":"Example Account", "realm":"3d885c.sip.example.com", "call_recording":{ "account":{ "inbound":{ "onnet":{ "enabled":false }, "offnet":{ "enabled":false } }, "outbound":{ "onnet":{ "enabled":false }, "offnet":{ "enabled":false } } }, "endpoint":{ "inbound":{ "onnet":{ "enabled":false }, "offnet":{ "enabled":true } }, "outbound":{ "onnet":{ "enabled":false }, "offnet":{ "enabled":true } } } } } } The current version of the recording API (for listing and fetching) is here: https://docs.2600hz.com/dev/applications/crossbar/doc/recordings/ Of course the original method of placing a recording start action in the callflow is still support as well.

Howdy, At this time there is no native capability in Kazoo but as Darren mentioned you could build a tool to parse the CSV and issue the appropriate API requests. There is an ancient tool (from 6 years ago) that might help get you started: https://github.com/2600hz-archive/xbar-importer Please note that this tool was written 6 years ago, is unlikely to work out of the box, and overly complicated. Its also worth mentioning that we do not support the xbar-importer just providing it as a possible reference, so your millage may vary.