Mike Jagdis wrote: > On Mon, May 21, 2007 at 11:12:11PM +0800, Steve Underwood wrote: > >> That might fix his problem, but why did he got garbage in the strings. >> Surely they should be set to something clean. >> > > I _suspect_ the callerid is just never initialised and the channel > drivers are expected to set _something_ even if it's nothing. > > >> I haven't heard back whether my changes to spandsp to handle the >> additional forms of DTMF CLI have solved the Kuwait guy's problem. I >> think he needed entry to terminate on the "C" for things to work. If >> things work for him now, we can clean up your patch to use spandsp to >> break up the strings in a DTMF caller ID. >> > > Isn't C the normal terminator? With only the calling party number > actually required and that can follow either A (usually) or D (Taiwan). > Most forms of DTMF CLI have a "#" at the end, and that is what spandsp was scanning for until last week. Now it looks for "#" or "C", and that seems safe with any type of CLI I know - i.e. the ones terminating with "#" don't have any "C" digits in them, and vice versa.
Steve _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
