From: Ryan H. <dre...@gm...> - 2010-03-18 17:40:53
|
I know my script and dialplan are handing the CID info just fine, if I remove the adhocnumber = *0 option from a line I can then pickup the <intercom> line, dial *0 manually and everything works just fine. the CID info is broken as soon as I try to use the adhocnumber option to dial the intercom automatically. Cheers, -Ryan On Thu, Mar 18, 2010 at 11:05 AM, Ryan Hunt <dre...@gm...> wrote: > here is a couple devices and there lines, first of all I have this in [general] > hotline_enabled=no > > [SEP001C58F106DD](797X) > devicetype = 7970 ; device type > (see below) > trustphoneip = yes ; The phone > has a ip address. It could be private, so if the phone is behind NAT > nat=off ; Device NAT > support (default Off > description = Kitchen ; Give a > description to the Phone (Displayed in the Right Top Corner on the > phone) > button = line,2001 > > > [SEP0021A0D97FEA](791X) > devicetype = 7906 ; device type > (see below) > trustphoneip = yes ; The phone > has a ip address. It could be private, so if the phone is behind NAT > nat=off ; Device NAT > support (default Off > description = Bedroom ; Give a > description to the Phone (Displayed in the Right Top Corner on the > phone) > button = line,2002 > > > [2001](defaultline) > id = 1861 ; future use > pin = 1234 ; future use > label = <intercom> ; button line > label (7960, 7970, 7940, 7920) > description = Intercom ; top diplay description > cid_name = Kitchen ; caller id name > cid_num = 2001 ; caller id number > adhocnumber = *0 > > [2002](defaultline) > id = 1861 ; future use > pin = 1234 ; future use > label = <intercom> ; button line > label (7960, 7970, 7940, 7920) > description = Intercom ; top diplay description > cid_name = Bedroom ; caller id name > cid_num = 2002 ; caller id number > adhocnumber = *0 > > Cheers, > -Ryan > > On Thu, Mar 18, 2010 at 9:44 AM, Ceschia, Marcello > <mar...@gm...> wrote: >> Hello Rya, >> >> can you post your device configuration for this device and the attached lines, please? >> >> Marcello >> >> >> Am 18. März 2010 16:28:59 schrieb Ryan: >>> in chan_sccp.c the following lines I commented out and got no caller-id instead of 'hotline', it still ignored what I configured for the line.. Looking at the code its obvious that the adhoc setting just dumps it into a hotline function and that has hard-coded cid values. >>> >>> sccp_copy_string(hotline->cid_name, "hotline", sizeof(hotline->cid_name)); >>> sccp_copy_string(hotline->cid_num, "hotline", sizeof(hotline->cid_name)); >>> >>> the script is simple, it takes 2 arguments.. the cid_num and cid_name >>> >>> #!/usr/local/bin/bash >>> asteriskdir=/var/spool/asterisk/outgoing/ >>> outdir=/usr/local/share/asterisk/agi-bin/intercom/ >>> debugfile=/tmp/debugfile >>> >>> startchan=2000 >>> endchan=2002 >>> >>> for (( channel=$startchan ; channel <= $endchan ; channel++ )) do >>> >>> if [[ $1 != $channel ]]; then >>> echo Channel: SCCP/$channel/aa=1wb > $outdir$channel-conf >>> echo Context: add-to-intercom >> $outdir$channel-conf >>> echo Extension: start >> $outdir$channel-conf >>> echo Priority: 1 >> $outdir$channel-conf >>> echo WaitTime: 30 >> $outdir$channel-conf >>> echo CallerID: $2 \<$1\> >> $outdir$channel-conf >>> echo $outdir$channel-conf >> $debugfile >>> >>> chown _asterisk._asterisk $outdir*conf >>> mv $outdir*conf $asteriskdir >>> sleep .20 >>> fi >>> done >>> >>> and here is the dialplan, >>> [intercom] >>> exten => *0,1,AGI(allcall.agi|${CALLERID(num)}|${CALLERID(name)}) >>> exten => *0,2,Conference(5555/MTV) >>> exten => h,1,Hangup >>> >>> exten => *2000,1,Dial(SCCP/2000/aa=1wb,ringer=silent) >>> exten => *2001,1,Dial(SCCP/2001/aa=1wb,ringer=silent) >>> exten => *2002,1,Dial(SCCP/2002/aa=1wb,ringer=silent) >>> >>> [add-to-intercom] >>> exten => start,1,Conference(5555) >>> exten => h,1,Hangup >>> >>> All works fine except cid_name and cid_num that are passed to my script are both 'hotline' and not '2000' -'2002' >>> >>> Cheers, >>> -Ryan >>> >>> On Mar 18, 2010, at 8:48 AM, Diederik de Groot wrote: >>> >>> > Hi Ryan, >>> > >>> > Can you attach the AGI script and the dialplan piece which fires the AGI script so we can have look. Have you added some verbose printing in your dialplan to figure out if you really do not get the Extension which starts the connection. Maybe your script looses this information somewhere. >>> > >>> > Regards, >>> > >>> > Diederik >>> > >>> > On Wed, 2010-03-17 at 00:08 -0600, Ryan wrote: >>> >> >>> >> Been working on getting a 1-way intercom system setup, after fighting a few things I got it all working. >>> >> >>> >> Here is how I have it setup, very similar to what you'll find on the voip-info wiki >>> >> >>> >> each phone has an unshared line labeled <intercom>, with an extension in the 2000-2099 range. >>> >> all these lines are configured for: adhocnumber = *0 >>> >> >>> >> *0 extension has a agi script that fires off an outbound an auto-answer connection (for all 20xx extensions) to a app_conference room and then joins the conference room as a moderator. >>> >> >>> >> The problem is since I am using the adhocnumber = to automatically fire off the intercom when the line button is selected, All calls appears to originate from "Hotline" and the CID info I specified for that line is not honored. >>> >> >>> >> This causes several issues since I cannot tell what extension the conference originated from, the biggest is that I cannot pass the phone's extension to my AGI script. This makes it impossible to code any logic to prevent the script from calling the same extension that started the intercom. >>> >> >>> >> Every other phone joins the conference room but has no idea who started it (just reads Hotline), and the phone that starts the intercom conference gets an inbound call on the <intercom> line and it will continue to just ring until it eventually times out. >>> >> >>> >> Any suggestions to work around this issue? I dont think the adhocnumber option should over-ride the line's CID info. If I select another line and dial *0 it rings all the <intercom> lines and shows proper CID info. >>> >> >>> >> Cheers, >>> >> -Ryan >>> >> ------------------------------------------------------------------------------ >>> >> Download Intel® Parallel Studio Eval >>> >> Try the new software tools for yourself. Speed compiling, find bugs >>> >> proactively, and fine-tune applications for parallel performance. >>> >> See why Intel Parallel Studio got high marks during beta. >>> >> http://p.sf.net/sfu/intel-sw-dev >>> >> _______________________________________________ >>> >> Chan-sccp-b-discussion mailing list >>> >> Cha...@li... >>> >> https://lists.sourceforge.net/lists/listinfo/chan-sccp-b-discussion >>> >> >>> > >>> > ------------------------------------------------------------------------------ >>> > Download Intel® Parallel Studio Eval >>> > Try the new software tools for yourself. Speed compiling, find bugs >>> > proactively, and fine-tune applications for parallel performance. >>> > See why Intel Parallel Studio got high marks during beta. >>> > http://p.sf.net/sfu/intel-sw-dev_______________________________________________ >>> > Chan-sccp-b-discussion mailing list >>> > Cha...@li... >>> > https://lists.sourceforge.net/lists/listinfo/chan-sccp-b-discussion >>> >>> >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Chan-sccp-b-discussion mailing list >> Cha...@li... >> https://lists.sourceforge.net/lists/listinfo/chan-sccp-b-discussion >> > |