search for: cvshead

I have 1 x100p. Caller id works fine with the beta1 release. Cvshead releases fail with a combination of checksum and ss_thread errors? I'm concerned when beta2 or the 1.2 release comes out it will not work. I have been through the configs I can't find and changes that need to be made to get CVSHEAD to work. Thanks John Hill

The 1.2 beta1 works fine. When I install the current cvshead it gives me different errors: I have seen checksum errors, Got event ring 18, etc. all give empty callerid. I have an x100p. Thanks --john

...~PAsteriskSoundChannel()': asteriskaudio.cxx:167: `baseChannel' undeclared (first use this function) asteriskaudio.cxx:167: (Each undeclared identifier is reported only once for each function it appears in.) make[1]: ** [asteriskaudio.o] Erro 1 make[1]: Saindo do diret??rio `/home/jmoura/cvshead/h323/asterisk-oh323-0.6.3a/wrapper' make: ** [subdirs_all] Erro 1 Use Asterisk CVS-HEAD-07/20/04-12:29:16 currently running. Can anybody help myself? Thank you. Joao Carlos Moura

I am using viatalk as my voip provider and they use dtmf=rfc2833, but asterisk is not seeing any of the dtmf. I am using CVShead as of 8/26/05. Nothing in the logs indicates a dtmf is being seen. If I use my pots line it sees it fine. Any assistance would be appreciated. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com

I have 1.2.0 beta 1 running and it works fine. My x100p returns caller id with no problems. When I test the CVSHEAD callerid fails with checksum and len < 0 errors. I can run with the cvshead of zaptel and libpri with beta1 but only the beta1 source works for caller id. Any source after beta1 fails. Thanks --john

For years we've had the following simple context for outgoing calls: [outtrunk] ; match any NANP, and strip leading 1 off exten => _1XXXXXXXXXX,1,StripMSD,1 ; dial outbound on trunk group 1 exten => _XXXXXXXXXX,2,Dial,Zap/g1/${EXTEN} But when I upgraded on Friday to the latest CVSHEAD, this no longer works. If I send 13115552368 to this context, I get a message like pbx.c: Channel 'Zap/361-1' sent into invalid extension '3115552368' in context 'outtrunk', but no invalid handler I tried adding a separate line to match 10D: exten => _XXXXXXXXXX,1,D...

...and there are no alarms. We see the connection on the console from the incoming user as seen below, if the user hangs up it disconnects properly, we can also do a zap destroy and disconnect the user. It seems that bi-directional communication is alright. We were running 1.0.7 but upgraded to CVSHEAD to see if a fix existed. Console Output: -- Accepting call from '414944XXXX' to '80094042XX' on channel 2/24, span 4 -- Executing Wait("Zap/48-1", "3") in new stack -- Executing Answer("Zap/48-1", "") in new stack -- Executin...

I have a problem that is probably so "doh" I will be embarrassed. However, I have spent all evening on this with no success: I have the following setup (asterisk cvshead as of today) 10 Channel EuroISDN<=>Asterisk<=>Meridian What I can do: Call from outside into the asterisk, dial an extension, and pass through to the meridian. WooHoo. What I can't do: Call from outside (firstnum) into the asterisk , dial an extension which calls an outside numbe...

I have been successfully connected (incoming and outgoing) to FWD for a very long time. A few months ago, I changed from SIP-based FWD service to IAX2-based, and that went fine as well, both incoming and outgoing. At the time, I was running Asterisk 1.0.3 Stable. I rarely use the service, so other than noticing that I was always successfully registered to FWD, I didn't make or receive calls