In the default dialplan, it bridges a call to voicemail using these actions: <action application="answer"/> <action application="sleep" data="1000"/> <action application="bridge" data="loopback/app=voicemail:default ${domain_name} ${dialed_extension}"/> I have found the the following also seems to work: <action application="answer"/> <action application="sleep" data="1000"/> <action application="voicemail" data="default ${domain_name} ${dialed_extension}"/> My question is why does the default dialplan use a bridge to loopback instead of just calling the voicemail app directly? What is the difference? -- Steve
It is just there as an example of one way to use loopback to call other applications. <snip>
It also allows an attended transfer to voicemail to work. -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/loopback-tp7589565p7589575.htm... Sent from the freeswitch-users mailing list archive at Nabble.com.
On Tue, Apr 9, 2013 at 3:45 PM, Jeff Lenk <jeff@jefflenk.com> wrote:
It also allows an attended transfer to voicemail to work.
I get it. If you use application="voicemail", and do an attended transfer, you can login and set it up to play a message, but when you complete the transfer, the first party will go back to the place as if he had dialed voicemail directly. Furthermore, if you get a call, and then conference your voicemail, you can both be listening to your messages, but as soon as you hang up, the called party will get switched to "Please enter your password." Bridging to loopback/app=voicemail solves these problems. Thank you. -- Steve
participants (3)
-
Jeff Lenk
-
Steven Schoch
-
Vik Killa