{"id":687,"date":"2019-12-02T09:48:30","date_gmt":"2019-12-02T01:48:30","guid":{"rendered":"https:\/\/www.myvoipapp.com\/blog\/?p=687"},"modified":"2019-12-02T09:48:30","modified_gmt":"2019-12-02T01:48:30","slug":"monitor-events-in-ivr-call-flow","status":"publish","type":"post","link":"https:\/\/www.myvoipapp.com\/blog\/2019\/12\/02\/monitor-events-in-ivr-call-flow\/","title":{"rendered":"Monitor events in IVR call flow"},"content":{"rendered":"\n

In miniSIPServer, we can use IVR-XML script to enable our own services, such as automatic-attendant. With previous IVR-XML set, ‘callto’ action will invoke a call to destination and finish the whole IVR process.<\/p>\n\n\n\n

But if we want to monitor some events in the call flow, such as we want to check ‘busy’ event and change the IVR flow to a new action, what should we do? <\/p>\n\n\n\n

Now V37 is released and a key feature is updated in IVR-XML. We can use ‘monitor-events’ in ‘callto’ action to monitor some events and change the call flow if they are caused.<\/p>\n\n\n\n

For example, the ‘callto’ action can be configured as below.<\/p>\n\n\n\n

<action method=\"callto\" name=\"mainAction\">\n    <destination>100<destination>\n    <monitor-events>\n        <monitor-event detection=\"busy\" nextaction=\"callto101\"\/>\n    <\/monitor-events>\n<\/action><\/pre>\n\n\n\n
In this example, if the call invoked by ‘callto’ action is busy, IVR procedure will be changed to next action ‘callto101’. <\/p>\n\n\n\n
Please refer to IVR-XML document<\/a> for more details about “monitor-events” element.<\/p>\n\n\n\n
IVR-XML example<\/a>Download<\/a><\/div>\n\n\n\n
Above zip file is an example of new ‘callto’ action. You can save and unzip it into ‘xml’ sub-directory where miniSIPServer is installed and configure a new record to test it.<\/p>\n\n\n\n
\"Configure
Configure miniSIPServer to trigger IVR-XML<\/figcaption><\/figure><\/div>\n","protected":false},"excerpt":{"rendered":"
In miniSIPServer, we can use IVR-XML script to enable our own services, such as automatic-attendant. With previous IVR-XML set, ‘callto’ action will invoke a call to destination and finish the whole IVR process. But if we want to monitor some events in the call flow, such as we want to check ‘busy’ event and change the IVR flow to a new action, what should we do? Now V37 is released and a key feature is updated in IVR-XML. We can…<\/p>\n
 Read More  Read More<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[35,34,1,137],"tags":[267,266,71,265,69],"class_list":["post-687","post","type-post","status-publish","format-standard","hentry","category-minisipserver","category-minisipserver_cloud","category-releases","category-tech-documents","tag-call-flow","tag-event","tag-ivr","tag-v37","tag-xml"],"_links":{"self":[{"href":"https:\/\/www.myvoipapp.com\/blog\/wp-json\/wp\/v2\/posts\/687","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.myvoipapp.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.myvoipapp.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.myvoipapp.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.myvoipapp.com\/blog\/wp-json\/wp\/v2\/comments?post=687"}],"version-history":[{"count":6,"href":"https:\/\/www.myvoipapp.com\/blog\/wp-json\/wp\/v2\/posts\/687\/revisions"}],"predecessor-version":[{"id":696,"href":"https:\/\/www.myvoipapp.com\/blog\/wp-json\/wp\/v2\/posts\/687\/revisions\/696"}],"wp:attachment":[{"href":"https:\/\/www.myvoipapp.com\/blog\/wp-json\/wp\/v2\/media?parent=687"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.myvoipapp.com\/blog\/wp-json\/wp\/v2\/categories?post=687"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.myvoipapp.com\/blog\/wp-json\/wp\/v2\/tags?post=687"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}