Re: [Asterisk-Users] Answer on second ring - need it on first.
On Sat, 4 Oct 2003, Steven Critchfield wrote: > On Sat, 2003-10-04 at 12:02, Lists wrote: > > But would you then not be able to use caller id from the telco? > > CallerID on an analog line is sent between the first and second ring > normally. So if the requester wants callerid and first ring answer, he > will have to move to PRI. > > Some choices have drawbacks, of course PRI is usually just cost. BRI gies the signalling advantages, but without the costs. -- Jon Stockill [EMAIL PROTECTED] ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Answer on second ring - need it on first.
Steven Critchfield wrote: On Sat, 2003-10-04 at 12:02, Lists wrote: But would you then not be able to use caller id from the telco? CallerID on an analog line is sent between the first and second ring normally. So if the requester wants callerid and first ring answer, he will have to move to PRI. Some choices have drawbacks, of course PRI is usually just cost. Fortunately I do not require Caller ID. Adding usecallerid=no to zapata.conf has resulted in answering on the first ring. Interestingly it has also fixed a 196kB memory leak that occurs for every call to the X100P. This is outlined in Bug 356. Regards, Richard ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Answer on second ring - need it on first.
On Sat, 2003-10-04 at 12:02, Lists wrote: > But would you then not be able to use caller id from the telco? CallerID on an analog line is sent between the first and second ring normally. So if the requester wants callerid and first ring answer, he will have to move to PRI. Some choices have drawbacks, of course PRI is usually just cost. > On Sat, 4 > Oct 2003, Martin Pycko wrote: > > > Yeah, I'd put usecallerid=no since I bet it's set by default as yes. > > > > Martin > > > > On Sat, 4 Oct 2003, Richard Scobie wrote: > > > > > > > > > > > Martin Pycko wrote: > > > > take out usecallerid=yes in zapata.conf > > > > > > > > Martin > > > > > > > > > > > > > Thanks Martin, but my zapata.conf is : > > > > > > [channels] > > > echocancel=yes > > > echocancelwhenbridged=yes > > > busydetect=yes > > > busycount=6 > > > context=incoming > > > signalling=fxs_ks > > > group=1 > > > channel => 1-2 > > > > > > Perhaps I need a usecallerid=no in there. I'll test this when I'm back > > > at work. I have not changed this prior to rebuilding the source. > > > > > > Regards, > > > > > > ___ > > > 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 -- Steven Critchfield <[EMAIL PROTECTED]> ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Answer on second ring - need it on first.
But would you then not be able to use caller id from the telco? On Sat, 4 Oct 2003, Martin Pycko wrote: > Yeah, I'd put usecallerid=no since I bet it's set by default as yes. > > Martin > > On Sat, 4 Oct 2003, Richard Scobie wrote: > > > > > > > Martin Pycko wrote: > > > take out usecallerid=yes in zapata.conf > > > > > > Martin > > > > > > > > > Thanks Martin, but my zapata.conf is : > > > > [channels] > > echocancel=yes > > echocancelwhenbridged=yes > > busydetect=yes > > busycount=6 > > context=incoming > > signalling=fxs_ks > > group=1 > > channel => 1-2 > > > > Perhaps I need a usecallerid=no in there. I'll test this when I'm back > > at work. I have not changed this prior to rebuilding the source. > > > > Regards, > > > > ___ > > 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] Answer on second ring - need it on first.
Yeah, I'd put usecallerid=no since I bet it's set by default as yes. Martin On Sat, 4 Oct 2003, Richard Scobie wrote: > > > Martin Pycko wrote: > > take out usecallerid=yes in zapata.conf > > > > Martin > > > > > Thanks Martin, but my zapata.conf is : > > [channels] > echocancel=yes > echocancelwhenbridged=yes > busydetect=yes > busycount=6 > context=incoming > signalling=fxs_ks > group=1 > channel => 1-2 > > Perhaps I need a usecallerid=no in there. I'll test this when I'm back > at work. I have not changed this prior to rebuilding the source. > > Regards, > > ___ > 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] Answer on second ring - need it on first.
> After re-installing, I am finding that when dialling into an X100P, that
> Answer is now answering on the second ring, where it always used to
> answer on the first before.
>
> In the console, "Starting simple switch on 'Zap/1-1' appears halfway
> through the first ring and "Executing Answer("Zap/1-1", "") in new
> stack" appears at the end of the second.
>
> I cannot recall having changed anything previously, in order for it
> answer on the first, but I would really like the old behaviour back.
I'd suspect that behavior is the result of a problem I reported to
support, for which Martin worked/fixed a few weeks ago. The issue that
I was having resulted from using the X100P with a CO Centrex line that
rings with a Long & a Short (within the normal ring cycle) to indicate
an incoming call from an outside party. Although * was picking up the
line, apparently the CallerID timing mechanism within * was looking
for CallerID data after the first ring (the Long) and obviously that
data wasn't there and therefore CallerID constantly failed.
I really don't have a clue what was changed since I didn't have any
before/after source snapshot.
Rich
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Answer on second ring - need it on first.
Martin Pycko wrote: take out usecallerid=yes in zapata.conf Martin Thanks Martin, but my zapata.conf is : [channels] echocancel=yes echocancelwhenbridged=yes busydetect=yes busycount=6 context=incoming signalling=fxs_ks group=1 channel => 1-2 Perhaps I need a usecallerid=no in there. I'll test this when I'm back at work. I have not changed this prior to rebuilding the source. Regards, ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Answer on second ring - need it on first.
take out usecallerid=yes in zapata.conf
Martin
On Sat, 4 Oct 2003, Richard Scobie wrote:
> After some months of "Make updates", I have just deleted my Zaptel and
> Asterisk source directories and done "cvs checkout" 's of asterisk and
> zaptel, in order to clean up the trees.
>
> After re-installing, I am finding that when dialling into an X100P, that
> Answer is now answering on the second ring, where it always used to
> answer on the first before.
>
> In the console, "Starting simple switch on 'Zap/1-1' appears halfway
> through the first ring and "Executing Answer("Zap/1-1", "") in new
> stack" appears at the end of the second.
>
> I cannot recall having changed anything previously, in order for it
> answer on the first, but I would really like the old behaviour back.
>
> Thanks,
>
> 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
[Asterisk-Users] Answer on second ring - need it on first.
After some months of "Make updates", I have just deleted my Zaptel and
Asterisk source directories and done "cvs checkout" 's of asterisk and
zaptel, in order to clean up the trees.
After re-installing, I am finding that when dialling into an X100P, that
Answer is now answering on the second ring, where it always used to
answer on the first before.
In the console, "Starting simple switch on 'Zap/1-1' appears halfway
through the first ring and "Executing Answer("Zap/1-1", "") in new
stack" appears at the end of the second.
I cannot recall having changed anything previously, in order for it
answer on the first, but I would really like the old behaviour back.
Thanks,
Richard
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
