But as Captain Hook would say, "using number is "bad form" ". What does not bite us now will eventually get us in a future update.
-----Original Message----- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Jason Parker Sent: Tuesday, November 10, 2009 1:09 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Setting outgoing callerid on when using a PRI Doug Lytle wrote: > Dave Fullerton wrote: >> Note "num" and not "number" I don't know if that was a change from 1.4 >> to 1.6 or if Doug mistyped it. >> > > Not a mistype. I've been using number all along, but looking at the > docs shows that I've been incorrect. It must concatenate the number > down to num. Looks like I've got a little modifying to do this evening: > > > core show function CALLERID > livonia*CLI> > -= Info about function 'CALLERID' =- > > [Syntax] > CALLERID(datatype[,<optional-CID>]) > > [Synopsis] > Gets or sets Caller*ID data on the channel. > > [Description] > Gets or sets Caller*ID data on the channel. The allowable datatypes > are "all", "name", *num*, "ANI", "DNID", "RDNIS". > Uses channel callerid by default or optional callerid, if specified. > > Doug > The documentation is correct, but the way the check really works, is that it reads the first 3 chars and matches it to "num". This means that "num", "number", and "numnumnumIloveapplesauce" would all technically match. _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users