[Asterisk-Users] Strange T1 Problem - FIXED plus new question

[Steven Critchfield]

On Fri, 2004-04-16 at 10:46, Ryan Thrash wrote:
> First, check zapata.conf to see what is in there. Next, I've not heard 
> of any luck with the name portion on T1s, but the number can be changed 
> for us.

The name portion is no problem if you are on a PRI. I personally have
had fun spoofing the callerid during some prank calls to my friends. 

In a channelized T1 like is mentioned below though, you don't have
enough signaling to specify it. FATIK, you can oply specify the outgoing
digits via some prearranged length and protocol similar to callerid and
dnis on inbound calls. I'm not sure if asterisk supports this on
channelized T1. 

> On Apr 16, 2004, at 10:30 AM, Mike Machado wrote:
> 
> >
> >>>
> >> You can usually get CLI on an E&M robbed bit T1 by configuring it 
> >> right.
> >> Instead of just sending you the DNIS as a string of DTMF they usually
> >> send *<cli>*<dnis>*. The DNIS and CLI may be swapped, and there may be
> >> less than 3 *s in the string - wonderful consistency, eh? :-\
> >
> > I am getting CallerID and DNIS on the inbound calls. What I really need
> > is to be able to set callerID on outbound calls. I am trying to set the
> > callerid using SetCIDNum just before using Dial on a zap channel, but 
> > it
> > looks like the switch guys have it set to always stamp the same 
> > callerID
> > on the my outbound calls no matter what I put in SetCIDNum or what
> > channel on the T1 I use. Is this a misconfiguration of the switch or a
> > limitation of the signaling protocol? If its the switch, can you give 
> > me
> > any pointers as to what I could ask them to look for, or if its the
> > protocol, do you know any other signaling protocol that lets me set
> > outbound callerID (besides PRI)?
> 

-- 
Steven Critchfield  <critch at basesys.com>