Made a mistake there... 18 was passed as was the first argument
(WhichInc) but the others were not.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brandon
Mackie
Sent: July 8, 2007 5:49 AM
To: Users Mailing List - Non-Commercial Discussion
Subject: [Callweaver-users] Dial proc changed in rc4?

Sorry yet another issue I found while trying to upgrade to rc4. I
noticed that it is expecting commas instead of | in most applications so
I have gone through and fixed this. Previously when called from a MySQL
dial plan | was the only acceptable separator in most commands. (Goto
1,1,1 wouldn't be treated correctly but Goto 1|1|1 would). I noticed
that a dial command with a proc was not passing the arguments any more.

app  | appdata
-----|------------------------------------------------------------------
--------------
Set  | WhichInc=1_1_0|WhichItem=exten
Dial |
SIP/[EMAIL PROTECTED]|15|gmtM(calltest^${WhichInc}^${WhichItem}^18^${CH
ANNEL})

That worked fine in the May 31 build of 1.1.99. It was not passing any
of the arguments to calltest in rc4. I tried switching all of the | to
commas as well making it:

app  | appdata
-----|------------------------------------------------------------------
--------------
Set  | WhichInc=1_1_0,WhichItem=exten
Dial |
SIP/[EMAIL PROTECTED],15,gmtM(calltest^${WhichInc}^${WhichItem}^18^${CH
ANNEL})

This time the third argument (18) was passed but nothing else was.
According to "show application Dial" nothing has changed. Am I missing
something?

_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users
_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users

Reply via email to