Quantcast
Channel: Developer Group
Viewing all articles
Browse latest Browse all 1888

Forum Post: RE: Using moml with "Prompt and Collect Service" to create conferences

$
0
0
Hi sc, You'll have to find a way to specify the actual connection ID, not "conn:this". I looked through RFC-5707, and XMS's MSML guide ( www.dialogic.com/.../XMS_MSMLUser.pdf ), and couldn't find any reference to this syntax. Please correct me if I'm wrong, but I think the only reason to think that "conn:this" might work is because verification.moml has this in it (not because any document suggests it should work). The reason it works in verification.moml is a very limited case. There's nothing special about "conn:this" actually. If you're loading an MSML script by specifying it with  ";moml=" in the SIP URI, the MSML server looks for the first instance of the text target="*anything*" and replaces that *anything* with the actual connection ID of the call. It won't work for any arguments other than "target=" , it won't work for any subsequent "target=" arguments, and it won't work for your usual MSML scripts carried in SIP INFO messages. Basically for your use case, you're going to have to go beyond static scripts, and dynamically generate the MSML with the correct connection IDs and conference IDs. Sorry, the special case that verification.moml uses doesn't seem to be documented, but hopefully the above should help you to understand what's really going on. Best Regards,  Greg B.

Viewing all articles
Browse latest Browse all 1888

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>