FASTDEVICE

I have several callflows that use "Groups" within Ring Groups from the previous UI. I can no longer find a way to create or manage these groups in Monster.

Thanks for the clarification.

I deleted and recreated, but need to wait the hour, as you mentioned.

Any thoughts why devices would not show in the Advanced Provisioner? And when I go to create them through the +Device interface, it returns "Access Forbidden." 

From our prior testing, it worked correctly by stopping the recording and allowing the callflow to VM. This needs to be fixed.

Thanks, we consider it a rather significate bug considering it's a callflow element that doesn't work correctly and wastes storage. What I'm really not liking is that I MUST test every scenario before deploying.

Thanks for confirming. I'm spending a lot of time on call recording as my team is working the feature into our new portal. Is there a Jira bug on this issue?

If I have a callflow configured as: Start Recording -> Ring Group -> Stop Recording -> Voicemail, the voicemail fails to play.   I have the Ring Group set to ring in order.

I may have read your response wrong, thinking it was CallerID. I will see if it matches any call id in the call records.

Not for Outbound, here is a real filename produced by an outbound call (ip address removed):  call_recording_105559734@[IP address].mp3

When an outbound call is recoded using the "no_match" case, the filename format being saved doesn't supply enough information to be useful. i.e. call_recording_[some number]@[IP address].mp3  Is there a way to include detail to identify the to/ from?

I'm looking for a good codec for use over 3g/4g and iLBC is highly recommended. Is iLBC supported?

Looking for a way to receive an inbound call on a realm's SIP address. I see how to do this outbound, but inbound is another matter.

I discovered an interesting way to provide on-demand'ish outbound recording without having to transfer to a recorded channel during a call (as suggested above). The "ish" part meaning the user would have to initiate an outbound call with the intent to record. So here is goes... create a callflow, for my example "*99" and begin with the call record widget.  Second, add a media file stating "Recording Enabled" to confirm. (or you can reverse the first two steps as not to record the media file.) and last, add the DISA widget without a PIN. (Make sure if you have an automated attendant, restrict extension access with a regexp; this is always a good idea anyway) When a user wants to record an outbound call they dial "*99" hear the confirmation and wait for the dial tone. Then dial a number and that call will be recorded.

I realize you're relaying the information, but metaflows is one of the originally documented features. How in the world is this still under development... I dare ask what is the timeline for completion?  

temp disabled or under development ? I have a client that is requesting recording on demand.

My development team is in needs of some technical assistance. Here is the request they asked me to post. Thanks in advance! ---snip I have been trying to get metaflows working for on demand call recording. Below is the metaflow object I have been using. I have tried several different versions playing with different parameters. Nothing seems to work. I have attached this to both the account and to a device. I have not tried attaching to a callflow, but that is not what I want to do. The URL is a 'capture' service that allows me to see the request. I have successfully used it when placing a call recording element in a callflow. Any help would be greatly appreciated'   "metaflows": {       "numbers": {         "8": {           "module": "record_call",           "data": {             "action": "stop"           }         },         "9": {           "module": "record_call",           "data": {             "action": "start",             "method": "put",             "url": "http://requestb.in/13gt1so1?recording=",             "time_limit": 1200,             "format": "mp3"           }         }       },       "patterns": {         "^1(\\d+)$": {           "module": "callflow"         }       },       "binding_digit": "*",       "digit_timeout_ms": 800,       "listen_on": "both",       "owner_id": "account id removed"     }

ah, it's only available if the number is configured for trunking...

correct me if I'm wrong, but doesn't the new "Number Manager" have a failover feature? "If your phone system is unreachable for any reason, we can redirect a caller to an alternate phone number or VoIP device. If the Failover number is an external number this call will cost you for both inbound and outbound."

@Aaron, FASTDEVICE is in... 

Any traction on accessing VMs from the API? I want to MOVE VMs from one box to another and link a VM message to a callflow. The latter for portal usage when the computer is not equipped with speakers. This way a user can select a VM from the web interface and listen via a click-to-call.

Thanks for sharing Issac. The Yealink support site shows the most current firmware for the T28P is x.73.0.50. Is the firmware you are referencing even new than that? If so, will it be posted to their site or somewhere else for manual upgrade?

Thanks for the clarification, but yikes what a mess. Back to snooping with wireshark.

Thanks @lazedo. Does Asterisk and Broadsoft follow a different standard from the ones you are referring? Even Yealink, with their new line of phones, spent months implementing a working version of BLF that is compatible with FreeSWITCH based PBXs.

I'm working with several offshore IP phone manufactures to widen our selection of compatible phones w/ 2600hz's network. However, they are all having the same difficulty in implementing BLF presence messaging for FreeSWITCH.  Can anyone point me to a definitive and well documented whitepaper on BLF presence for FreeSWITCH and any addendum that may be required for how 2600hz may affect that implementation?