Hi All, We have a production system running 1.4.25.1 and yesterday we upgraded it to 1.4.36. Basically we use this system to generate scheduled calls via .call files.
Sample .call file used: Channel: local/111111...@context-out WaitTime: 30 CallerId: 333333333 Extension: 222222222 Context: context-out Priority: 1 With the sample call file in 1.4.25.1 the behavior was: 1 - The asterisk box calls 111111111 with callerid 333333333 2 - When 111111111 answer the call asterisk calls 222222222 with callerid 111111111 With the sample call file in 1.4.36 the behavior is: 1 - The asterisk box calls 111111111 with callerid 333333333 2 - When 111111111 answer the call asterisk calls 222222222 with callerid 333333333 Basically now the callerid specified in the call file is used for the two call legs and before was only used on the first call leg. Anyone knows why the callerid behavior changed between this two versions and if there is any way to have 1.4.36 actuate like 1.4.25.1? Thanks for your help! Regards, Toni.
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
