Re: [asterisk-users] CallerID masking
Alex, This would fix only one of 2 problems. By setting the CDR source variables, I'm still left with the monitor variable and any others that may come up in the future. There was another email saying I should just set the monitor file name as well. Since I'm using auto_mon, I'm not sure that would even work. This seems like something most companies would want to have working. How would your average company handle this? Rob Alex Balashov wrote: > On Thu, 19 Apr 2007, Rob Schall said something to this effect: > >> Hello all, >> >> I currently have all outgoing calls set to mask the caller id so it will >> always appear to be coming from our main number. The problem I'm having >> though, is with both the call detail in mysql and with the automon >> (recording) feature. It shows the originating number as the number I >> masked it to, rather than the actual person calling. How can I go about >> having both the destination see our main number, but our internally >> logging see the correct #? > > I haven't tried this one, but you could try assign the source caller > ID number to a temporary variable, mask the caller ID, then Set() one of > the CDR variables (${CDR(src)} I presume) to the value of the temporary > variable... in the dialplan. > > -- Alex > > -- > Alex Balashov <[EMAIL PROTECTED]> > ___ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] CallerID masking
Hello Rob, try to set che MONITOR_FILENAME as something containing the internal extension befor emasking the CID hope it helps Edoardo Rob Schall ha scritto: Hello all, I currently have all outgoing calls set to mask the caller id so it will always appear to be coming from our main number. The problem I'm having though, is with both the call detail in mysql and with the automon (recording) feature. It shows the originating number as the number I masked it to, rather than the actual person calling. How can I go about having both the destination see our main number, but our internally logging see the correct #? ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Ing. Edoardo Serra WeBRainstorm S.r.l. Via Pio FoĆ 83/C 10126 - Torino Tel: +39 011 678 100 Fax: +39 011 678 275 ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] CallerID masking
On Thu, 19 Apr 2007, Rob Schall said something to this effect: Hello all, I currently have all outgoing calls set to mask the caller id so it will always appear to be coming from our main number. The problem I'm having though, is with both the call detail in mysql and with the automon (recording) feature. It shows the originating number as the number I masked it to, rather than the actual person calling. How can I go about having both the destination see our main number, but our internally logging see the correct #? I haven't tried this one, but you could try assign the source caller ID number to a temporary variable, mask the caller ID, then Set() one of the CDR variables (${CDR(src)} I presume) to the value of the temporary variable... in the dialplan. -- Alex -- Alex Balashov <[EMAIL PROTECTED]> ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] CallerID masking
Hello all, I currently have all outgoing calls set to mask the caller id so it will always appear to be coming from our main number. The problem I'm having though, is with both the call detail in mysql and with the automon (recording) feature. It shows the originating number as the number I masked it to, rather than the actual person calling. How can I go about having both the destination see our main number, but our internally logging see the correct #? ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users