Although it shouldn't make a difference, try:
channel => 1-2
As well, did you run ztcfg after you installed the new card? I've found
sometimes I've had run ztcfg a couple times before Asterisk would "kick
in" and recognize a new card.
On Sat, 2004-08-21 at 02:49 -0500, spectro wrote:> I just added a second X100P card to my * server, altough it seems to
> be working * seems to be ignoring it:
>
> zaptel.conf:
> -----------------
> fxsks=1-2
> loadzone=us
> defaultzone=us
>
> zapata.conf:
> ------------------
> context=inbound-analog
> signalling=fxs_ks
> group=1
> channel => 1
> channel => 2
>
>
> I created a couple of test extensions:
>
> ; test extensions
> exten => 4390,1,Dial(Zap/g1/4189)
> exten => 4390,2,Congestion
> exten => 4391,1,Dial(Zap/1/4189)
> exten => 4391,2,Congestion
> exten => 4392,1,Dial(Zap/2/4189)
> exten => 4392,2,Congestion
>
> 4391 works fine, 4392 doesn't:
>
> -- Executing Dial("IAX2/vperez@vperez/2",
"Zap/2/4189") in new stack
> Aug 21 02:47:36 NOTICE[426002]: app_dial.c:714 dial_exec: Unable to create
chann
> el of type 'Zap'
> == Everyone is busy/congested at this time
>
> I don't know what's wrong, Zap/2 shows fine in the zap channels
list:
>
> pbx*CLI> zap show channels
> Chan Extension Context Language MusicOnHold
> pseudo inbound-analog
> 1 inbound-analog
> 2 inbound-analog
>
>
> Any ideas?
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
--
Mike Benoit <ipso@snappymail.ca>