Hi Sherwood I actually do want "dynamic" CLID as I tried to make clearer
>> I don't know if this makes it any clearer - >> >> An internal call from Ext123 should send 123 as the CLID to SIP/Ext400 but should >> send 442071110123 to SIP/TheWorld but an external call from 44123455667788 should >> send the received CLID 44123455667788 to both. So over the provider connection the CLID will be different for different calls. Setting the main office number in sip.conf is fine as a default but as the code/dialplan needs to set cli for some calls I actually set CLID for all calls. This setting and onward transmission by provider works fine. So what I am trying to do is call 2 different sip endpoints AT THE SAME TIME presenting different AND VARIABLE CLIs. If Nasir's trick is not recommended what is the best way to achieve this. As a newbie to Asterisk advise and best practice gained from user experience is always welcome. Paddy -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sherwood McGowan Sent: 20 August 2010 04:58 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Calling Line Identity - any ideas On Thu, Aug 19, 2010 at 7:46 PM, Nasir Iqbal <[email protected]> wrote: > Hi, >> there's still no conceivable reason > What can be? except performance! (as asterisk has to create one > additional leg and bridge it) Which is very conceivable to those who > are dealing with high load traffic. > And what will be the option, if other outgoing call requires different > custom CLI while using the same trunk? > Regards > -- > Nasir Iqbal > > ICT Innovations > http://www.ictinnovations.com/ > > > -- > _____________________________________________________________________ > -- 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 > First, the reason is, why use a BAD IDEA when there's perfectly good solutions in front of the user.... There was no mention on this ONE call going outbound over the trunk needing a different CID...the request was as follows: Client needs to call an INTERNAL extension, where the INTERNAL CallerID will be used, and at the SAME TIME, a call to an EXTERNAL number (which would necessitate USING THEIR PROVIDER TRUNK), using the EXTERNAL CallerID.... Now, p-lease tell me how just configuring the damned trunk's outbound CID is NOT more sensible, efficient, and just friggin' COMMON SENSE TO START WITH...over using a Local channel call, which would require slightly more typing, and using something that I've almost NEVER found a good reason to use, and if you'd care to search the damn archives, you'll see that I was pushing upwards of 5k CONCURRENT CALLS back in 2005, WITH 1.4 Trunk and the RealTime addiiton (which was experimental)... For the love of whatever you find holy and good and true...don't come at me like that...I'm really not in the mood anymore...I put 3-4 solid years of helpjng newbies figure out why shit didn't work, reporting REAL bugs and issues to thew developers and even assisting with some of the fixes....I feel entitled (yes, I know that's an asshole thing to say) to a little common respect.... Now...anyone for a pint? I'm off to vent some frustration with people who jump on the WRONG bandwagon and try to take over.... Sherwood Mother-F'in' McGowanb... Telecommunications and Tattooing.... You konw anyone else who combines those two professions? I'd like to buy that guy a drink! -- _____________________________________________________________________ -- 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
