Re: [Asterisk-Users] FXO mode
Andy Powell wrote: Can't find the message in a search.. but below is a msg retreved from my archive.. this is what Mark sent a little while ago I have no idea if it actually does anything to the card, but on a modprobe I do get a msg saying it's using CTR21 Andy I'm in Paris right now and can't test this change, but I've been researching the DAA and there are a few international settings I can change, so I've changed the driver in CVS so that you can specify the operational mode. Try modprobe wcfxo opermode=1 if you're in most of Europe and that should switch to CTR21 mode which slightly modifies a few of the electrical characteristics of the DAA. As we add modes you'll be able to see them with modprobe wcfxo opermode=-1 and then doing a dmesg. Anyway all you folks that had some trouble like this try it out and let me know if it makes any difference. Mark I guess in his haste to help out the people who were having a problem, Mark looked at the wrong data sheet when he wrote this patch. I have corresponded with him and confirmed that this code requires the Global DAA chipset, which is not fitted to the current X100P cards. The mail I was referring to is: http://lists.digium.com/pipermail/asterisk-users/2003-August/017825.html Regards, Richard ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
On Fri, 2003-08-15 at 11:42, Richard Scobie wrote: I guess in his haste to help out the people who were having a problem, Mark looked at the wrong data sheet when he wrote this patch. I have corresponded with him and confirmed that this code requires the Global DAA chipset, which is not fitted to the current X100P cards. So the question is does changing to CTR21 do anything at all with the existing cards? If it does nothing then OK, all I want to know is that it doesn't do anything bad. Much as I, and others, hate France Telecom I'd rather not nuke their exchange. I've got CID no problem. I have a problem with it not hanging up, but I am sure this is software not hardware, as it only happens if voicemail starts and the caller hangs up to exit, if they use # everything is OK. -- Dave Cotton [EMAIL PROTECTED] ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
On Wed, 2003-08-13 at 18:36, Andy Powell wrote: On 13/08/2003 at 17:46 Dave Cotton wrote: in the file wcfxo.c the following structure is initialised as below which would suggest that FCC is wrong for France or pretty well all of Europe. errm, FCC mode is for the US. CTR21 is for Europe - you even pasted the info in your message! Exactly, the question really is how do you change it? I've even commented out the FCC bit and it still gives the same in /var/log/messages -- Dave Cotton [EMAIL PROTECTED] ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
Andy Powell wrote: FCC mode is for the US. CTR21 is for Europe - you even pasted the info in your message! Exactly, the question really is how do you change it? modprobe wcfxo opermode=1 HTH Andy This switch (opermode=1) is redundant with the current X100P cards, as it changes register contents that are specific to the Global version of the chipset on the card. The X100P currently out there uses the USA Japan chipset, and thus does not achieve the intended result. The register concerned deals with the impedance presented to the line connected to the card - 600 ohms (US) vs various complex impedances used in other countries. For internationalised FXO cards, see Mark's recent comments, in the thread Does Wildcard x100p support BT Caller ID in UK? Regards, Richard ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
On Wed, 2003-08-13 at 09:46, Dave Cotton wrote: I've had a few problems with my system holding the line after a call has been made, just now I rebooted and noticed the following in /var/log/messages When you say holding the line, do you mean that asterisk still believes a channel is in use even after you hang up? If so, I've seen the same thing happen several times with the X100P. If I do show channels it will show one of my SIP phones connected to one of the outside lines, but if I check that SIP phone, it is not in use, and there is no way to re-activate the channel from the SIP phone. Running soft hangup zap channel will hangup the channel (you don't need to reboot). I'm not entirely sure what causes it. So far, I've only seen it happen from 2 of our 9 SIP phones, but they're the ones most often on the phone. It always involves an outside line, so I believe the X100P is the problem, but I can't be sure. What other information can I gather to pinpoint the problem? ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
Hi,
I exactly got the same problem on the Belgian network. I have tried to recompile the
wcfx0 driver with the FCC line
commented and I have created a zone for Belgium in zonedata.c (see below with the
values I know. I'm not sure of
call wait, dial recall and record tone). Everything works fine but I still got the
same problem. The system does
not detect a external line hangup.
extract of zonedate.c
[...]
{ 8, be, Belgium, { 1000, 3000 },
{
{ ZT_TONE_DIALTONE, 450 },
{ ZT_TONE_BUSY, 450/150,0/150 },
{ ZT_TONE_RINGTONE, 450/1000,0/3000 },
/* XXX I'm making up the congestion tone XXX */
{ ZT_TONE_CONGESTION, 450/250,0/250 },
/* XXX I'm making up the call wait tone too XXX */
{ ZT_TONE_CALLWAIT, 450/300,0/1 },
/* XXX I'm making up dial recall XXX */
{ ZT_TONE_DIALRECALL,
!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,350+440 }
,
/* XXX I'm making up the record tone XXX */
{ ZT_TONE_RECORDTONE, 1400/500,0/15000 },
{ ZT_TONE_INFO, !950/330,!1400/330,!1800/330,0 },
{ ZT_TONE_STUTTER,
!440/100,!0/100,!440/100,!0/100,!440/100,!0/100,!440/100,!0/100,!440/100,
!0/100,!440/100,!0/100,440 } },
[...]
/etc/zaptel.conf
#
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#
#
fxsks=1
loadzone=be
defaultzone=be
DAA mode is CTR21 as I can see in /var/log/messages
Aug 13 20:31:41 ws183 kernel: wcfxo: DAA mode is 'CTR21'
Any other ideas on how to solve this issue?
Regards,
Dave Cotton wrote:
I've had a few problems with my system holding the line after a call has
been made, just now I rebooted and noticed the following in
/var/log/messages
Aug 13 17:23:15 Sheriff kernel: wcfxo: DAA mode is 'FCC'
in the file wcfxo.c the following structure is initialised as below
which would suggest that FCC is wrong for France or pretty well all of
Europe.
static struct fxo_mode {
char *name;
int ohs;
int act;
int dct;
int rz;
int rt;
int lim;
int vol;
} fxo_modes[] =
{
{ FCC, 0, 0, 2, 0, 0, 0, 0 }, /* US */
{ CTR21, 0, 0, 3, 0, 0, 3, 0 }, /* Austria, Belgium,
Denmark, Finland, France, Germany,
Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands,
Norway, Portugal, Spain, Sweden, Switzerland, and UK */
Any thoughts as to if this is the root of the problem.
--
Dave Cotton
Directeur
Linux Autrement
193 rue Marcel Cerdan
84270 Vedene
04 90 23 30 81
Internet Sheriff Technology revendeur en France
http://www.linuxautrement.com
IAX 17004902330
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
--
Perceval Helpdesk Team
[EMAIL PROTECTED]
Perceval Technologies sa/nv
Rue Tenbosch, 9
B-1000 Brussels
BELGIUM
Tel: +32-2-6409194
Fax: +32-2-6403154
URL: http://www.perceval.be/
E-mail for general information: [EMAIL PROTECTED]
E-mail for technical information: [EMAIL PROTECTED]
This e-mail message contains legally PRIVILEGED and CONFIDENTIAL
information intended for the use of the addressee only. If you are not
the intended recipient of this message, please notify the undersigned
by telephone or e-mail reply and destroy this message and any attachments.
Any views or opinions presented in this e-mail are solely those of
the author and do not necessarily represent those of Perceval. The
integrity and security of this message cannot be guaranteed and it may
be subject to data corruption, interception, unauthorised amendment,
viruses and unforeseen delays, for which we accept no liability.
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
On Thu, 2003-08-14 at 12:24, Andy Powell wrote: Can't find the message in a search.. but below is a msg retreved from my archive.. this is what Mark sent a little while ago I have no idea if it actually does anything to the card, but on a modprobe I do get a msg saying it's using CTR21 Andy I'm in Paris right now and can't test this change, but I've been researching the DAA and there are a few international settings I can change, so I've changed the driver in CVS so that you can specify the operational mode. Try modprobe wcfxo opermode=1 if you're in most of Europe and that should switch to CTR21 mode which slightly modifies a few of the electrical characteristics of the DAA. As we add modes you'll be able to see them with modprobe wcfxo opermode=-1 and then doing a dmesg. Anyway all you folks that had some trouble like this try it out and let me know if it makes any difference. Mark ___ Thanks Andy. The stage I'm at at the moment is that I've removed the code for the US and so dmesg will show CTR21 without the modprobe option. But I don't think that is the whole problem. Last night I posted showing that the problem is repeatable and only occurs in one certain circumstance. I think it is within voicemail.c. If the caller exits voicemail by pressing # the line is dropped correctly, if they just hang up voicemail continues to record. I put some debugging statements into voicemail.c and I think that a condition statement is never reached so the line is held up. The routine in question is 14 pages long, so it reminds me of my Cobol days when we used to lay the printouts along the corridor to debug them. As far as the option to modprobe is concerned couldn't zaptel.conf be used for this as it would be more obvious, I only heard about the option from your post last night. -- Dave Cotton [EMAIL PROTECTED] ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode 2147483647.1060797007@[192.168.1.210] 1060794258.27544.62.camel@RobinHood.LinuxAutrement.com
On Wed, 2003-08-13 at 11:13, Emmanuel Bergmans wrote: In order to test CTR21, I was forced to comment the line in the source file as I did not find a define or a zaptel.conf directive. It's really bad but... In my case this change has not solved the problem (see previous posting) Well, I'm in the US, and I still have the problem, so I'm assuming the problem isn't some European-only problem. Mine is sporadic, however - if you're getting the same thing consistently, then maybe your problem is worse. Steve ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
In order to test CTR21, I was forced to comment the line in the source file as I did
not find a define or a
zaptel.conf directive. It's really bad but... In my case this change has not solved
the problem (see previous
posting)
in wcfx0.c
[...]
fxo_modes[] =
{
/* { FCC, 0, 0, 2, 0, 0, 0, 0 }, */
/* US */
{ CTR21, 0, 0, 3, 0, 0, 3, 0 }, /* Austria, Belgium, Denmark, Finland,
France, Germany,
Greece, Iceland, Ireland, Italy,
Luxembourg, Netherlands,
Norway, Portugal, Spain, Sweden,
Switzerland, and UK */
};
[...]
Dave Cotton wrote:
On Wed, 2003-08-13 at 18:50, Iain Stevenson wrote:
Assuming this is on incoming calls,
Yes
the most usual source of the problem is
that the telco exchange either doesn't send a disconnect pulse or the wcfxo
driver doesn't recognise the format used.
Exactly, if * is stuck in FCC mode CTR21 will be a foreign language.
Somewhere in the code I should be able to either #define what I want or
zaptel.conf should be able to set it
--
Dave Cotton [EMAIL PROTECTED]
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
--
Perceval Helpdesk Team
[EMAIL PROTECTED]
Perceval Technologies sa/nv
Rue Tenbosch, 9
B-1000 Brussels
BELGIUM
Tel: +32-2-6409194
Fax: +32-2-6403154
URL: http://www.perceval.be/
E-mail for general information: [EMAIL PROTECTED]
E-mail for technical information: [EMAIL PROTECTED]
This e-mail message contains legally PRIVILEGED and CONFIDENTIAL
information intended for the use of the addressee only. If you are not
the intended recipient of this message, please notify the undersigned
by telephone or e-mail reply and destroy this message and any attachments.
Any views or opinions presented in this e-mail are solely those of
the author and do not necessarily represent those of Perceval. The
integrity and security of this message cannot be guaranteed and it may
be subject to data corruption, interception, unauthorised amendment,
viruses and unforeseen delays, for which we accept no liability.
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
Errm, no... does that mean you'll personally check to see if my line is busy or not ;P will try it now... Andy *** REPLY SEPARATOR *** On 14/08/2003 at 09:58 Martin Pycko wrote: Did you try BUSYDETECT_MARTIN in asterisk/Makefile ? regards Martin On Thu, 14 Aug 2003, Andy Powell wrote: Hi Dave, I have a similar problem, I tried using busydetect and busycount but calls kept being dropped at random intervals. It didn't seem to matter what i set the busycount to. I guess it's a case of deciding which is more important... You can also limit the length of the voicemails using ; Maximum length of a voicemail message maxmessage=180 in voicemail.conf which cuts down the length of the recorded dial tone... Andy Thanks Andy. The stage I'm at at the moment is that I've removed the code for the US and so dmesg will show CTR21 without the modprobe option. But I don't think that is the whole problem. Last night I posted showing that the problem is repeatable and only occurs in one certain circumstance. I think it is within voicemail.c. If the caller exits voicemail by pressing # the line is dropped correctly, if they just hang up voicemail continues to record. I put some debugging statements into voicemail.c and I think that a condition statement is never reached so the line is held up. The routine in question is 14 pages long, so it reminds me of my Cobol days when we used to lay the printouts along the corridor to debug them. As far as the option to modprobe is concerned couldn't zaptel.conf be used for this as it would be more obvious, I only heard about the option from your post last night. -- Dave Cotton [EMAIL PROTECTED] ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
FCC mode is for the US. CTR21 is for Europe - you even pasted the info in your message! Exactly, the question really is how do you change it? modprobe wcfxo opermode=1 HTH Andy ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] FXO mode
On Wed, 2003-08-13 at 18:50, Iain Stevenson wrote: Assuming this is on incoming calls, Yes the most usual source of the problem is that the telco exchange either doesn't send a disconnect pulse or the wcfxo driver doesn't recognise the format used. Exactly, if * is stuck in FCC mode CTR21 will be a foreign language. Somewhere in the code I should be able to either #define what I want or zaptel.conf should be able to set it -- Dave Cotton [EMAIL PROTECTED] ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
On 13/08/2003 at 17:46 Dave Cotton wrote:
in the file wcfxo.c the following structure is initialised as below
which would suggest that FCC is wrong for France or pretty well all of
Europe.
errm,
FCC mode is for the US. CTR21 is for Europe - you even pasted the info
in your message!
See below
Andy
static struct fxo_mode {
char *name;
int ohs;
int act;
int dct;
int rz;
int rt;
int lim;
int vol;
} fxo_modes[] =
{
{ FCC, 0, 0, 2, 0, 0, 0, 0 }, /* US */
{ CTR21, 0, 0, 3, 0, 0, 3, 0 }, /* Austria, Belgium, Denmark,
Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands,
Norway, Portugal, Spain, Sweden, Switzerland, and UK */
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] FXO mode
Assuming this is on incoming calls, the most usual source of the problem is that the telco exchange either doesn't send a disconnect pulse or the wcfxo driver doesn't recognise the format used. I've unfortunately forgotten the exact situation but, when a call finishes, a telco exchange in the US will momentarily remove/reverse line power. That tells the fxo card, hence *, that the call is over. If such a pulse isn't present * assumes the call is still in progress. This has been discussed on the list in the past so it's worth googling. Iain --On Wednesday, August 13, 2003 12:09 pm -0400 Joe Antkowiak [EMAIL PROTECTED] wrote: I've had this happen with the x100p and analog phones as well... When I moved to a t1 and a channel bank, the problem never happened again... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Meyers Sent: Wednesday, August 13, 2003 12:04 PM To: Asterisk List Subject: Re: [Asterisk-Users] FXO mode On Wed, 2003-08-13 at 09:46, Dave Cotton wrote: I've had a few problems with my system holding the line after a call has been made, just now I rebooted and noticed the following in /var/log/messages When you say holding the line, do you mean that asterisk still believes a channel is in use even after you hang up? If so, I've seen the same thing happen several times with the X100P. If I do show channels it will show one of my SIP phones connected to one of the outside lines, but if I check that SIP phone, it is not in use, and there is no way to re-activate the channel from the SIP phone. Running soft hangup zap channel will hangup the channel (you don't need to reboot). I'm not entirely sure what causes it. So far, I've only seen it happen from 2 of our 9 SIP phones, but they're the ones most often on the phone. It always involves an outside line, so I believe the X100P is the problem, but I can't be sure. What other information can I gather to pinpoint the problem? ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
Can't find the message in a search.. but below is a msg retreved from my archive.. this is what Mark sent a little while ago I have no idea if it actually does anything to the card, but on a modprobe I do get a msg saying it's using CTR21 Andy I'm in Paris right now and can't test this change, but I've been researching the DAA and there are a few international settings I can change, so I've changed the driver in CVS so that you can specify the operational mode. Try modprobe wcfxo opermode=1 if you're in most of Europe and that should switch to CTR21 mode which slightly modifies a few of the electrical characteristics of the DAA. As we add modes you'll be able to see them with modprobe wcfxo opermode=-1 and then doing a dmesg. Anyway all you folks that had some trouble like this try it out and let me know if it makes any difference. Mark ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users *** REPLY SEPARATOR *** On 14/08/2003 at 20:48 Richard Scobie wrote: Andy Powell wrote: FCC mode is for the US. CTR21 is for Europe - you even pasted the info in your message! Exactly, the question really is how do you change it? modprobe wcfxo opermode=1 HTH Andy This switch (opermode=1) is redundant with the current X100P cards, as it changes register contents that are specific to the Global version of the chipset on the card. The X100P currently out there uses the USA Japan chipset, and thus does not achieve the intended result. The register concerned deals with the impedance presented to the line connected to the card - 600 ohms (US) vs various complex impedances used in other countries. For internationalised FXO cards, see Mark's recent comments, in the thread Does Wildcard x100p support BT Caller ID in UK? Regards, Richard ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
Did you try BUSYDETECT_MARTIN in asterisk/Makefile ? regards Martin On Thu, 14 Aug 2003, Andy Powell wrote: Hi Dave, I have a similar problem, I tried using busydetect and busycount but calls kept being dropped at random intervals. It didn't seem to matter what i set the busycount to. I guess it's a case of deciding which is more important... You can also limit the length of the voicemails using ; Maximum length of a voicemail message maxmessage=180 in voicemail.conf which cuts down the length of the recorded dial tone... Andy Thanks Andy. The stage I'm at at the moment is that I've removed the code for the US and so dmesg will show CTR21 without the modprobe option. But I don't think that is the whole problem. Last night I posted showing that the problem is repeatable and only occurs in one certain circumstance. I think it is within voicemail.c. If the caller exits voicemail by pressing # the line is dropped correctly, if they just hang up voicemail continues to record. I put some debugging statements into voicemail.c and I think that a condition statement is never reached so the line is held up. The routine in question is 14 pages long, so it reminds me of my Cobol days when we used to lay the printouts along the corridor to debug them. As far as the option to modprobe is concerned couldn't zaptel.conf be used for this as it would be more obvious, I only heard about the option from your post last night. -- Dave Cotton [EMAIL PROTECTED] ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
--On Thursday, August 14, 2003 12:58 pm +0200 Dave Cotton [EMAIL PROTECTED] wrote: Last night I posted showing that the problem is repeatable and only occurs in one certain circumstance. I think it is within voicemail.c. If the caller exits voicemail by pressing # the line is dropped correctly, if they just hang up voicemail continues to record. I put some debugging statements into voicemail.c and I think that a condition statement is never reached so the line is held up. I'm just a little concerned that this is patching the symptoms without identifying the correct cause. If a caller presses '#' that tells asterisk the call is over and can be destroyed. This is a very different process from the call being terminated by a signal sent from the remote exchange. Iain ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
Ok, I've changed it to use BUSYDETECT_MARTIN and I'll see how it goes and let you know.. thanks for the tip... Andy *** REPLY SEPARATOR *** On 14/08/2003 at 09:58 Martin Pycko wrote: Did you try BUSYDETECT_MARTIN in asterisk/Makefile ? regards Martin On Thu, 14 Aug 2003, Andy Powell wrote: Hi Dave, I have a similar problem, I tried using busydetect and busycount but calls kept being dropped at random intervals. It didn't seem to matter what i set the busycount to. I guess it's a case of deciding which is more important... You can also limit the length of the voicemails using ; Maximum length of a voicemail message maxmessage=180 in voicemail.conf which cuts down the length of the recorded dial tone... Andy Thanks Andy. The stage I'm at at the moment is that I've removed the code for the US and so dmesg will show CTR21 without the modprobe option. But I don't think that is the whole problem. Last night I posted showing that the problem is repeatable and only occurs in one certain circumstance. I think it is within voicemail.c. If the caller exits voicemail by pressing # the line is dropped correctly, if they just hang up voicemail continues to record. I put some debugging statements into voicemail.c and I think that a condition statement is never reached so the line is held up. The routine in question is 14 pages long, so it reminds me of my Cobol days when we used to lay the printouts along the corridor to debug them. As far as the option to modprobe is concerned couldn't zaptel.conf be used for this as it would be more obvious, I only heard about the option from your post last night. -- Dave Cotton [EMAIL PROTECTED] ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] FXO mode
On Wed, 2003-08-13 at 19:41, Steve Meyers wrote: Well, I'm in the US, and I still have the problem, so I'm assuming the problem isn't some European-only problem. Mine is sporadic, however - if you're getting the same thing consistently, then maybe your problem is worse. OK Getting a bit further. In the wcfxo.c there is static int opermode = 0; so FCC will always be the day. But now I can describe different scenarios: 1. Caller hangs up after 2 or 3 rings - no problem. 2. Caller gets answered by unavail message and presses # - no problem 3. Caller gets answered by unavail message and hangs up - line stays up and voicemail keeps recording. 4. Caller gets answered and either party hangs up - no problem. It's then probably voicemail that doesn't receive the hang up. Dave Cotton Directeur Linux Autrement 193 rue Marcel Cerdan 84270 Vedene 04 90 23 30 81 Internet Sheriff Technology revendeur en France http://www.linuxautrement.com IAX 17004902330 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
