Re: [asterisk-users] Fwd: Problems with zap following 1.4.6 install
Thanks for responding Russell! What output do you get if you run module unload chan_zap.so == Unregistered application 'ZapSendKeypadFacility' and then module load chan_zap.so ? == Registered application 'ZapSendKeypadFacility' == Parsing '/etc/asterisk/zapata.conf': Found [Jun 30 07:46:51] WARNING[12132]: chan_zap.c:903 zt_open: Unable to specify channel 1: No such device or address [Jun 30 07:46:51] ERROR[12132]: chan_zap.c:7157 mkintf: Unable to open channel 1: No such device or address here = 0, tmp-channel = 1, channel = 1 [Jun 30 07:46:51] ERROR[12132]: chan_zap.c:10463 build_channels: Unable to register channel '1' Hopefully you'll be able to tell me what the above means! I'm using the same zapata.comf that I used with 1.2... Thanks, H ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Fwd: Problems with zap following 1.4.6 install
Figured it out. I forgot that /etc/zaptel.conf got clobbered during the install. Once I fixed that and ran: /sbin/ztcfg - It worked. Zaptel.conf looks like this: loadzone = us defaultzone=us fxoks = 1-2 fxsks = 4 I have 1 FXO module 2 FXS modules. Thanks for putting me on the right track!! H On 6/30/07, hugolivude [EMAIL PROTECTED] wrote: Thanks for responding Russell! What output do you get if you run module unload chan_zap.so == Unregistered application 'ZapSendKeypadFacility' and then module load chan_zap.so ? == Registered application 'ZapSendKeypadFacility' == Parsing '/etc/asterisk/zapata.conf': Found [Jun 30 07:46:51] WARNING[12132]: chan_zap.c:903 zt_open: Unable to specify channel 1: No such device or address [Jun 30 07:46:51] ERROR[12132]: chan_zap.c:7157 mkintf: Unable to open channel 1: No such device or address here = 0, tmp-channel = 1, channel = 1 [Jun 30 07:46:51] ERROR[12132]: chan_zap.c:10463 build_channels: Unable to register channel '1' Hopefully you'll be able to tell me what the above means! I'm using the same zapata.comf that I used with 1.2... Thanks, H ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Fwd: Problems with zap following 1.4.6 install
hugolivude wrote: Just upgrading to 1.4.6 from 1.2. SIP channels work OK, but not zap. I have a TDM400 w/ an FXO 2 FXS. I built libpri 1.4.0 first then zaptel 1.4.3. Menuselect had a * beside chan_zap and I loaded the wcusb wctdm before building asterisk. In the CLI zap show channels returns no such command. chan_zap.so exists in /usr/lib/asterisk/modules. What could be the problem how to fix? What output do you get if you run module unload chan_zap.so and then module load chan_zap.so ? -- Russell Bryant Software Engineer Digium, Inc. ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FWD problems
On Wed, 24 Dec 2003, denon wrote:
I've been having issues getting FWD to work. I posted this same Q to the
FWD forum (no responses yet), but I was hoping someone here had some insight:
My setup is like this:
sip.conf:
register = 21542:[EMAIL PROTECTED]/6002 ; Free World Dialup
[fwd.pulver.com]
type=peer
host=fwd.pulver.com
fromuser=21542
fromdomain=fwd.pulver.com
username=21542
secret=password
In extensions.conf:
; Free World Dialup
[fwd]
exten = _10113.,1,Dial(SIP/${EXTEN:[EMAIL PROTECTED])
exten = _10113.,2,Congestion
(I use a 10113 prefix for FWD numbers).
We're chatting to friends in the UK right now so seems to work for me.
Steve
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FWD problems
--On Wednesday, December 24, 2003 07:12:05 -0600 denon [EMAIL PROTECTED] wrote: I've got it running through Asterisk - all working fine from a SIP standpoint. I can dial FWD numbers like 612/613/etc and everything works. However, if I dial *18005551212 or *408xxx (say, a USA number), I either get a fast busy or a This service is only available to FreeWorld Dialup members. I have exactly this problem and posted a bug report to FWD about a week ago - no response yet. It's bizarre that FWD recognises you to dial another user but not to call outside their network. Sounds more like a FWD problem than a * problem to me. Iain ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] FWD problems
--On Wednesday, December 24, 2003 07:12:05 -0600 denon [EMAIL PROTECTED] wrote: I've got it running through Asterisk - all working fine from a SIP standpoint. I can dial FWD numbers like 612/613/etc and everything works. However, if I dial *18005551212 or *408xxx (say, a USA number), I either get a fast busy or a This service is only available to FreeWorld Dialup members. I have exactly this problem and posted a bug report to FWD about a week ago - no response yet. It's bizarre that FWD recognises you to dial another user but not to call outside their network. Sounds more like a FWD problem than a * problem to me. Read the fwd announcement. Jeff Pulver mentioned the fact that * users cannot use the free holiday calls, since FWD cannot be sure that * is not being used by more than 1 user at the same time. Arnold ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] FWD problems
--On Wednesday, December 24, 2003 6:35 pm +0100 Arnold Ligtvoet [EMAIL PROTECTED] wrote: Read the fwd announcement. Jeff Pulver mentioned the fact that * users cannot use the free holiday calls, since FWD cannot be sure that * is not being used by more than 1 user at the same time. Where in this announcement: On Free World Dialup, go ahead and dial: *1 (area code) Number. We have arranged to pick up the costs to allow members of the Free World Dialup community to place calls into the US and Canada for Free during the 2003 holiday season. While the offical press release will follow later today or tomorrow, you can help out in the beta-trials of this holiday gift today. Feel free to share the holiday spirit and cheer. :-) .. does it say * cannot be used? Remember, I tried this a week ago and got the this service is available to FWD members only message. Pulver posted the message mentioning the restriction on 21 December - I've been waiting since December 18 for a reply to my original report of a problem. Still, there seems to be a you get what you pay for theme to many of today's posts and this clearly applies to support on FWD. Naybe we should remove the signature from * that enables FWD to identify * systems :-) Iain ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] FWD problems
Still, there seems to be a you get what you pay for theme to many of today's posts and this clearly applies to support on FWD. Naybe we should remove the signature from * that enables FWD to identify * systems :-) That certainly seems the case for today's theme... It is certainly the right of any company or person to define the rules of their service. Since I don't pay for either Asterisk or FWD then I appreciate the service that is provided and try not to crusify them when things don't go right. This entire VoIP is still rather experimental. If I want guaranteed service then I'll pay some provider for it... THEN.. and only then will a service level be expected. Robert ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] FWD problems
--On Wednesday, December 24, 2003 10:06 pm +0100 rnc Info Lists [EMAIL PROTECTED] wrote: Still, there seems to be a you get what you pay for theme to many of today's posts and this clearly applies to support on FWD. Naybe we should remove the signature from * that enables FWD to identify * systems :-) That certainly seems the case for today's theme... It is certainly the right of any company or person to define the rules of their service. Since I don't pay for either Asterisk or FWD then I appreciate the service that is provided and try not to crusify them when things don't go right. This entire VoIP is still rather experimental. If I want guaranteed service then I'll pay some provider for it... THEN.. and only then will a service level be expected. That's fair comment but I think FWD should have put a correct message on their system for asterisk users. It wouldn't have taken much effort. FWD and * complement each other and should benefit from each other's success. Indeed * is cited on the FWD web site and mentioned by Jeff Pulver at his VON events. It seems a little unfortunate that FWD is assuming all * systems are a front for hundreds of users and banning them. Iain ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FWD problems
On Wed, 24 Dec 2003, Iain Stevenson wrote: I have exactly this problem and posted a bug report to FWD about a week ago - no response yet. It's bizarre that FWD recognises you to dial another user but not to call outside their network. Sounds more like a FWD problem than a * problem to me. Suspect your INVITE into FWD isn't authenticated so FWD thinks of you as a foreigner. Perhaps a sip debug will help see what is happening. Steve ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
