I was using the Mad Boss example and I was getting parse errors, I traced it down to the following line, <action application="conference_set_auto_outcall" data="${group_call(sales)}"/> when group_call gets expanded it adds the default dial string for each member of the group which ends up looking something like this. [sip_invite_domain=10.195.94.25,presence_id=1001@xxx.xxx.xxx.xxx]sofia/internal/sip:1001@xxx.xxx.xxx.xxx, [sip_invite_domain=10.195.94.25]error/user_not_registered The parse error I got "Cannot create outgoing channel of type [presence_id=1003@10.195.94.25]error cause: [CHAN_NOT_IMPLEMENTED]" indicated that it was treating the comma inside the brackets as a separator between 2 dial strings. I worked around this for now by editing the default config for the directory to remove presence_id from the dial string and it's working. This appears to be a bug in the parser as I was getting this error with the default configurations. Thanks, Duvid Rottenberg
How recent is your version of FreeSWITCH? Also, which users in that group were registered and which were not? I'd like to see if others can reproduce this behavior under similar conditions using the latest HEAD. -MC On Wed, Aug 24, 2011 at 5:41 PM, Duvid Rottenberg <adrottenberg@gmail.com>wrote:
I was using the Mad Boss example and I was getting parse errors, I traced it down to the following line,
<action application="conference_set_auto_outcall" data="${group_call(sales)}"/>
when group_call gets expanded it adds the default dial string for each member of the group which ends up looking something like this.
[sip_invite_domain=10.195.94.25,presence_id=1001@xxx.xxx.xxx.xxx ]sofia/internal/sip:1001@xxx.xxx.xxx.xxx, [sip_invite_domain=10.195.94.25]error/user_not_registered
The parse error I got "Cannot create outgoing channel of type [presence_id=1003@10.195.94.25]error cause: [CHAN_NOT_IMPLEMENTED]" indicated that it was treating the comma inside the brackets as a separator between 2 dial strings. I worked around this for now by editing the default config for the directory to remove presence_id from the dial string and it's working.
This appears to be a bug in the parser as I was getting this error with the default configurations.
Thanks, Duvid Rottenberg
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
I pulled the latest from git the begining of this weekl. I am running it on windows server 2008 (although I don't think that makes a difference). Only user 1001 was registered. On Fri, Aug 26, 2011 at 1:35 PM, Michael Collins <msc@freeswitch.org> wrote:
How recent is your version of FreeSWITCH? Also, which users in that group were registered and which were not? I'd like to see if others can reproduce this behavior under similar conditions using the latest HEAD. -MC
On Wed, Aug 24, 2011 at 5:41 PM, Duvid Rottenberg <adrottenberg@gmail.com> wrote:
I was using the Mad Boss example and I was getting parse errors, I traced it down to the following line,
<action application="conference_set_auto_outcall" data="${group_call(sales)}"/>
when group_call gets expanded it adds the default dial string for each member of the group which ends up looking something like this.
[sip_invite_domain=10.195.94.25,presence_id=1001@xxx.xxx.xxx.xxx]sofia/internal/sip:1001@xxx.xxx.xxx.xxx, [sip_invite_domain=10.195.94.25]error/user_not_registered
The parse error I got "Cannot create outgoing channel of type [presence_id=1003@10.195.94.25]error cause: [CHAN_NOT_IMPLEMENTED]" indicated that it was treating the comma inside the brackets as a separator between 2 dial strings. I worked around this for now by editing the default config for the directory to remove presence_id from the dial string and it's working.
This appears to be a bug in the parser as I was getting this error with the default configurations.
Thanks, Duvid Rottenberg
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
This should probably be reported to Jira so It does not get forgotten. Thanks -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Parsing-Error-on-conference-se... Sent from the freeswitch-users mailing list archive at Nabble.com.
I put the logs in the pastebin at http://pastebin.freeswitch.org/17220 On Sat, Aug 27, 2011 at 2:52 PM, Brian West <brian@freeswitch.org> wrote:
I would like to see the full logs something returned is not properly escaped to be used in an originate string. /b On Aug 27, 2011, at 11:34 AM, Jeff Lenk wrote:
This should probably be reported to Jira so It does not get forgotten. Thanks
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (4)
-
Brian West
-
Duvid Rottenberg
-
Jeff Lenk
-
Michael Collins