I can't think of a good way to do this. I'll theorize something that might work if you don't have too many inbound lines...
The gateway could, for each individual line, ring a different user that would be present on an operator's phone. Then you would know what line a call came in on. To dial out, you could program an access code based on that line number that would be passed to the gateway that would then trigger outbound routing to route out a particular trunk group. Your trunk groups would all have one line in them. This same principle would work for AudioCodes or Patton. I think in the Patton you could get around having multiple lines by having the Patton rewrite the FROM information to have it just display the line #. Mike On Mon, Feb 6, 2012 at 7:47 AM, Shawn Beard <[email protected]> wrote: > I need to figure out if there is a way to reliably initiate a *57 call > trace. We need to use it for things like threatening phone calls . Doing a > *57 allows the local law enforcement to get caller info from the phone > company. The *57 has to be dialed after hanging up from the call so you > have to be sure that you grab the SAME outside line that the call came in > on. I have multiple lines pooled together so grabbing the same line > doesn't usually happen. Does anyone know if there is a way to accomplish > this ? On our old system the line card port id was displayed on the phone > and we were able to dial a prefix and then the line ID so we got back on > the same line. > > > > > > > On 2/5/12 9:13 PM, "[email protected]" > <[email protected]> wrote: > > >Send sipx-users mailing list submissions to > > [email protected] > > > >To subscribe or unsubscribe via the World Wide Web, visit > > http://list.sipfoundry.org/mailman/listinfo/sipx-users > >or, via email, send a message with subject or body 'help' to > > [email protected] > > > >You can reach the person managing the list at > > [email protected] > > > >When replying, please edit your Subject line so it is more specific > >than "Re: Contents of sipx-users digest..." > >[please change the subject line when replying]Today's Topics: > > > > 1. Re: Sip Vicious and Remote Workers (George Niculae) > > 2. Re: Sip Vicious and Remote Workers (Tony Graziano) > > 3. Re: Confirming config roll out changes to 4.6? (Tony Graziano) > > 4. Auto Attendant (Roman Gelfand) > > 5. Re: Auto Attendant (Tony Graziano) > > 6. Re: Auto Attendant (Roman Gelfand) > > 7. Re: Auto Attendant (Tony Graziano) > >_______________________________________________ > >sipx-users mailing list > >[email protected] > >http://list.sipfoundry.org/mailman/listinfo/sipx-users > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Michael Picher, Director of Technical Services eZuce, Inc. 300 Brickstone Square**** Suite 201**** Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com ------------------------------------------------------------------------------------------------------------ Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab A gathering for - open source users, eZuce customers & eZuce partners Get the inside track on 4.6 and a glimpse at the future of sipXecs!
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
