Simon, Two problems here:
1. Set(CDR(accountcode)=200) is not setting the value for the outbound leg. The record before, detailing the context that the call is working through gets the change I make via CDR(), but there is a record of the actual call using Dial() (which is the record I'm concerned with for the billing) which retains all the account/extension details from the inbound leg. 2. We're operating a pre-paid system, so dealing with the billing end AFTER the call could be a problem. If the account doesn't have any dollars, user shouldn't be able to make the call... I'm not sure how to prevent this currently. To authenticate the user when they call in, I'm using VMAuthenticate(). Thanks for the help so far... -Erik -----Original Message----- From: Simon P. Ditner [mailto:[email protected]] Sent: Sunday, April 04, 2010 11:56 To: Erik Schwartz Cc: <[email protected]> Subject: Re: [on-asterisk] Creating a new channel You can set the account code field using the CDR() function, and use that for your billing. --- Simon P. Ditner On 2010-04-04, at 10:52 AM, "Erik Schwartz" <[email protected]> wrote: > I'm wondering if and how I can create a new channel for an outbound > leg of a > call. > > > > The scenario is, our subscribers will call an access number, where > they hit > an IVR and have to authenticate themselves. Once they're in, they > can then > place a call through our system. This whole routine is fine and is > working > now, my problem is when it comes to billing: > > > > I would like to bill the call to the extension that they authenticate > themselves to, but as it stands now, when I Dial(), it shows up in > the CDR > as the extension that received the call originally from the inbound > channel. > > > > > So I'm wondering if there's a way for me to send the outbound call > on a new > channel, or how can I attach that outbound call to the authenticated > extension? > > > > -Erik > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
