[Asterisk-Users] Re: TDM400P - All extensions have same CallerID

[Zachary Whitley]

On Sat, 2005-08-06 at 11:36 -0500, Larry Shields wrote:
> Check your "zapata.conf" file.  Your terminal profile options section under
> [channels] should be ended by adding the associated channel, i.e. channel =>
> 1
> 
> Sample two port config:
> 
> [channels]
> ;
> ; Default language
> ;
> language=en
> 
> ; Default terminal profile FXS PORT1
> ;
> context=internal
> signalling=fxo_ks
> usecallerid=yes
> callerid="Line 1" <2001>
> callwaiting=yes
> callwaitingcallerid=yes
> callreturn=yes
> echocancel=yes
> echocancelwhenbridged=yes
> rxgain=0.0
> txgain=0.0
> mailbox=2001
> group=1
> 
> channel => 1
> 
> ; Default terminal profile FXS PORT2
> ;
> context=internal
> signalling=fxo_ks
> usecallerid=yes
> callerid="Line 2" <2002>
> callwaiting=yes
> callwaitingcallerid=yes
> callreturn=yes
> echocancel=yes
> echocancelwhenbridged=yes
> rxgain=0.0
> txgain=0.0
> mailbox=2002
> group=1
> 
> channel => 2
> 
> 
> 
> "Mike Putnam" <asterisk at mikeputnam.com> wrote in message
> news:<003701c59a97$de0fe510$058fa8c0 at dragonship>...
> > I've been searching the forums and on the list to see if this has been
> > addressed. If it has, could someone point me to the thread to fix or at
> > least acknowledge it is an issue and what is causing it. Posting to the
> list
> > was last resort as I couldn't find a solution anywhere else.
> > 
> > Setup:
> > Asterisk at Home 1.3 (this is my first system, so path of least resistance)
> > Digium TDM400P (2 FXS on ports 1 & 2, 2 FXO on 3& 4)
> > 
> > My FXS extentions are 201 and 210. Both of my FXS extentions report being
> > the same extension when doing a *65. It is always the last extension
> > configured as well, in this case 210. In fact, when recording prompts,
> even
> > if I'm on extension 201, I have to tell the system that I'm on extension
> > 210. I deleted the second extention and 201 started acting properly. I
> added
> > a new extension (x400) and both are being reported as 400 now. To make
> > things even more confusing, calls can be placed to the proper extension,
> so 
> > it
> > seems to be something with CallerID, but I can figure out what it is. As 
> > stated,
> > this was my first system so I used AAH to get up and running fast and then
> > work backwards to learn and use the system. I started with AAH 1.1 and
> > everything worked fine for about 2 weeks, then I noticed a problem when I
> > started having messages on x201 but the light wasn't blinking. To the best
> > of my memory, when I started out I didn't have this problem. Both
> extensions
> > were acting normally. I didn't put on any AAH or Asterisk updates. I'm
> > running AAH 1.3 now just to see if it would fix the problem.
> > 
> > Any and all suggestions are greatly appreciated.
> > 
> > Mike
> > 

After messing around with the zapata.conf file I have a few questions.
What determines the scope of commands in the zapata.conf file? In
zapata.conf we're defining channels, correct? Since the config file is
kind of flat. (everything is under [channel]) What is the official start
and end of a channel block? Does it start with context= and end with
channel= ?

Why isn't there separate blocks?

ie.

[channel1]
...
...
...

[channel2]
...
...
...