Re: [asterisk-users] TDM400P incoming route for DID

2006-10-12 Thread Eric \ManxPower\ Wieling
[EMAIL PROTECTED] wrote: I am an asterisk newbie. I have successfully installed asterisk on Freebsd. The problem I am having is when I try to route based upon incoming DID. CALLERID(dnid) nor CDR(dst) have a number in them. Please help. Digium analog cards do not support DID service.

Re: [asterisk-users] TDM400P incoming route for DID

2006-10-12 Thread Eric \ManxPower\ Wieling
Alex Robar wrote: Analog routes (ie. copper telco lines) do not have DID information on them. Only digital lines (PRI, often VoIP DID) have this information sent alongside the call. Analog lines in the USA can support DID, but only using things like EM Wink which the Digium cards do not

Re: [asterisk-users] TDM400P incoming route for DID

2006-10-12 Thread Alex Robar
Thanks Eric, I didn't know that. The general answer I've always seen regarding analog lines was that they supported CID only, and never sent DID. Good to know... Thanks,Alex On 10/12/06, Eric ManxPower Wieling [EMAIL PROTECTED] wrote: Alex Robar wrote: Analog routes (ie. copper telco lines) do not

Re: [asterisk-users] TDM400P incoming route for DID

2006-10-12 Thread Eric \ManxPower\ Wieling
As far as I know any signaling protocol you can get on a Channelized Voice T-1 you can also get on analog lines. In fact these signaling protocols originated on analog lines and are simply emulated on voice T-1s. Notice I said Channelized Voice T-1, not ISDN PRI. Granted, analog lines with

[asterisk-users] TDM400P incoming route for DID

2006-10-11 Thread kim
I am an asterisk newbie. I have successfully installed asterisk on Freebsd. The problem I am having is when I try to route based upon incoming DID. CALLERID(dnid) nor CDR(dst) have a number in them. Please help. Thanks ___ --Bandwidth

Re: [asterisk-users] TDM400P incoming route for DID

2006-10-11 Thread Alex Robar
Analog routes (ie. copper telco lines) do not have DID information on them. Only digital lines (PRI, often VoIP DID) have this information sent alongside the call. What you need to do is change the context for each port you want redirected in zapata.conf, like