The predial routine must be run on the local;1 channel.
authorRichard Mudgett <rmudgett@digium.com>
Tue, 15 May 2012 19:36:26 +0000 (19:36 +0000)
committerRichard Mudgett <rmudgett@digium.com>
Tue, 15 May 2012 19:36:26 +0000 (19:36 +0000)
commitd5d984daa55590b70dfaa4e3b8d78563fe96d740
treec345f197644879d899b9d31a0466cf14cc5fc9a2
parent1ae31fd2a9d02857f6915778e528e81c77540543
The predial routine must be run on the local;1 channel.

When ast_call() operates on a local channel, it copies a lot of things
from the local;1 channel to the local;2 channel.  This includes among
other things, channel variables and party id information.

Other reasons it was a bad idea to run predial on the local;2 channel:

1) The channel has not been completely setup.  The ast_call() completes
the setup.

2) The local;2 caller and connected line party information is opposite to
any other channels predial runs on.  (And it hasn't been setup yet.)

* Partially back out -r366183 by removing the chan_local implementation of
the struct ast_channel_tech.pre_call callback.

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@366546 65c4cc65-6c06-0410-ace0-fbb531ad65f3
channels/chan_local.c