Okay, that makes it clear. Thank you.
Wolfgang
Daniele Orlandi wrote:
> On Wednesday 1 March 2006 11:05, Wolfgang Hottgenroth wrote:
>
>>>exten => _.,1,Macro(telcobri_out|${EXTEN})
>>>exten => _o-.,1,Macro(telcobri_out|${EXTEN}:2)
>>
>>Does have the :2 to appear in the curly braces or is this something else
>>than skipping the first two characters from ${EXTEN}?
>
>
> No, sorry, it's a typo, it should read as:
>
> exten => _.,1,Macro(telcobri_out|${EXTEN})
> exten => _o-.,1,Macro(telcobri_out|${EXTEN:2})
>
>
>>Could I do this routing AND passthru by modifying line 4 and 5to
>>
>>exten => _o-0[2-9].,1,Dial(VISDN/visdn0/${EXTEN:2})
>>exten => _o-Z.,1,Dial(VISDN/visdn0/${EXTEN:2})
>
>
> Yup, it should work.
>
>
>>What about line 17 (VISDNOverlapDial)? To be dropped completely?
>
>
> It still needs to be put in [intern-isdn]. VISDNOverlapDial() looks for that
> extension to know if it can start the PBX immediately and pass each digit or
> waiting for the number to be complete.
>
> Let me sum the procedure:
>
> You pick you the phone, it starts an empty overlap dialing, vISDN looks for
> extension 's' in [intern-isdn] and starts VISDNOverlapDial() [1]
>
> VISDNOverlapDial receives the digits you dial (suppose 1234) and looks if it
> finds a match with o-1234, if it can, it starts the PBX on that extension,
> otherwise it looks if the number can match and can match more.
>
> Uhm... better yet, I've uploaded a flow diagram at
>
> http://www.visdn.org/visdn_overlap_dialing_flow.png
>
> It's quite complicated but explains in detail what's going on :)
>
> [1] Note that VISDNOverlapDial() is not strictly mandatory, you can do all
> sorts of funny stuff at extension 's', like playing some file, dialing, etc..
>
> Ciao,
>
_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers
