On Wednesday 26 May 2004 19:42, Jon Lawrence wrote:
It looks like my missing digit problems are down to the dect phone I have
connected to my handytone ata-286. When i have my Binatone dect connected,
I only get the first 8 digits, if I connect my panasonic dect then I see
all the digits -
Tony Hoyle [EMAIL PROTECTED] wrote:
I forget how I determined the cadence values, as it was some time ago.
The values work for me.
Running asterisk in verbose mode prints the values out when it gets the
ring... It's actually calculated as a repeated subtraction from a
constant
value
I would love to test it, but I need some help with the zapata config
settings. In the US you can have up to 4 numbers on a line each with a
ring pattern. The ring patterns are:
Long ring - 1st number (this is a normal ring - like if you didn't have
distinctive ringing at all)
Double ring - 2nd
First of all thanks for the patch it works great,
but i think it breaks the distinctive ringing,
I have 2 incoming numbers in one x100p in contexts home1 and home2 but
'default' is always chosen has anyone else seen this?
if you need any more info just ask
Robb
Tony Hoyle wrote:
David J Carter
Cheers Tony.
Your a star.
Works a treat.
Dave
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Tony Hoyle
Sent: 28 May 2004 00:48
To: [EMAIL PROTECTED]
Subject: Re: [Asterisk-Users] Caller ID with BT CD50
David J Carter wrote:
Where would I find cdr
Robert Boardman [EMAIL PROTECTED] wrote:
First of all thanks for the patch it works great,
but i think it breaks the distinctive ringing,
I have 2 incoming numbers in one x100p in contexts home1 and home2 but
'default' is always chosen has anyone else seen this?
Yes - it does break the
Kevin,
Could you add this to
http://bugs.digium.com/bug_view_page.php?bug_id=0001719
Chris
- Original Message -
From: Kevin Walsh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 28, 2004 9:12 AM
Subject: RE: [Asterisk-Users] Caller ID with BT CD50
Robert Boardman [EMAIL
PROTECTED]
Subject: RE: [Asterisk-Users] Caller ID with BT CD50
Robert Boardman [EMAIL PROTECTED] wrote:
First of all thanks for the patch it works great,
but i think it breaks the distinctive ringing,
I have 2 incoming numbers in one x100p in contexts home1 and home2
but
'default' is always
Karl Dyson [EMAIL PROTECTED] wrote:
Just checked out asterisk stable and zaptel, patched using Tony's
patches (which worked, and compiled previously)
Then got this when applying your patch.
bash # cat ../chan_zap.c.diff | patch -p0
patching file channels/chan_zap.c
Hunk #1 succeeded at
Karl Dyson wrote:
Just tried to apply the patch:
Just checked out asterisk stable and zaptel, patched using Tony's
patches (which worked, and compiled previously)
Then got this when applying your patch.
bash # cat ../chan_zap.c.diff | patch -p0
patching file channels/chan_zap.c
Hunk #1 succeeded
: [EMAIL PROTECTED] [mailto:asterisk-users-
[EMAIL PROTECTED] On Behalf Of Kevin Walsh
Sent: 28 May 2004 12:07
To: [EMAIL PROTECTED]
Subject: RE: [Asterisk-Users] Caller ID with BT CD50
Karl Dyson [EMAIL PROTECTED] wrote:
Just checked out asterisk stable and zaptel, patched using Tony's
,
Karl
-Original Message-
From: [EMAIL PROTECTED] [mailto:asterisk-users-
[EMAIL PROTECTED] On Behalf Of Kevin Walsh
Sent: 28 May 2004 12:07
To: [EMAIL PROTECTED]
Subject: RE: [Asterisk-Users] Caller ID with BT CD50
Karl Dyson [EMAIL PROTECTED] wrote:
Just checked out
Karl Dyson [EMAIL PROTECTED] wrote:
Well compiles and runs OK, but it doesn't identify the dring. I only
started playing with it this morning (only realised it *did* dring when
I saw your it's broken dring post)
This is what I have in zapata.conf
dring1=95,0,0
Kevin Walsh wrote:
Yes - it does break the distinctive ring detection, but that's easily
sorted out.
Actually it's the first time I've ever heard of distinctive ring being
available in the UK... :)
The correct way would be to move the if (p-use_callerid == 2)
code within the existing if
Karl Dyson wrote:
Well compiles and runs OK, but it doesn't identify the dring. I only
started playing with it this morning (only realised it *did* dring when
I saw your it's broken dring post)
This is what I have in zapata.conf
dring1=95,0,0
dring1context=inbound-pstn-1
dring2=325,95,0
Tony Hoyle [EMAIL PROTECTED] wrote:
Kevin Walsh wrote:
Yes - it does break the distinctive ring detection, but that's easily
sorted out.
Actually it's the first time I've ever heard of distinctive ring being
available in the UK... :)
It costs the same as Caller*ID, so I just got it to
Kevin Walsh wrote:
I applied your new patch but it resulted in the caller hearing a ring
tone but no phones actually ringing. I don't have time to look into
it right now, but I'll take a look later and see what's going on.
I put my chan_zap.c back in and the re-tests were ok.
I've changed it
On Fri, 28 May 2004, Tony Hoyle wrote:
Actually it's the first time I've ever heard of distinctive ring being
available in the UK... :)
BT launched Call Sign sometime in 1996.
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
On Fri, 2004-05-28 at 10:27, Kevin Walsh wrote:
Chris Stenton [EMAIL PROTECTED] wrote:
Could you add this to
http://bugs.digium.com/bug_view_page.php?bug_id=0001719
I thought that, if it was confirmed as working for people other than
just me, Tony Hoyle might want to add it to his original
Tony Hoyle [EMAIL PROTECTED] wrote:
Kevin Walsh wrote:
I applied your new patch but it resulted in the caller hearing a ring
tone but no phones actually ringing. I don't have time to look into
it right now, but I'll take a look later and see what's going on.
I put my chan_zap.c back in
Kevin Walsh wrote:
Ok - now the phones ring but there are three problems:
1. The distinctive ring is not recognised - both types of ring are
directed to the same context.
No idea why that could happen - it's not obvious how detection works in the
first place though (not sure what it's
Tony Hoyle wrote:
That's the way the code is written (which is why you have 3 values in
the dring entry I think). There's an assumption in the code that it has
3 rings to compare with.
Actually it's worse than that... there is actually no terminator in the code.
It's looking for a distinct
Tony Hoyle wrote:
I've changed the patch to fix the buffer overrun, plus a hack to only
look for the dring values you specify, thus:
btw. It would be great if someone in the US can test these changes to make
sure I haven't broken the CID/DR on their side by doing this.
Tony
--
Te audire no
-Users] Caller ID with BT CD50
I keep rolling buffer of the last couple of seconds of the incoming
audio, so when the ring is detected the chan_zap driver can grab this
and feed it to the callerid processing routines.
If it's necessary to assign copyright to digium then there's no problem
doing
David J Carter wrote:
I have addes the ukcallerid=yes to my zapata.conf, and also got
callerid=asreceived set.
No idea what that option does...
The phones now ring without the screen showing starting simple switch 3-4
times, but alas no callerid on my GS phone.
Check your cdr-csv file to see if
callerid=asreceived
signalling=fxs_ks
channel = 1 : BT line
channel = 2 : Telewest line
Dave
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Tony Hoyle
Sent: 27 May 2004 22:31
To: [EMAIL PROTECTED]
Subject: Re: [Asterisk-Users] Caller ID with BT CD50
David J
David J Carter wrote:
Where would I find cdr-csv?
Usually in /var/log/asterisk
The line looks funny because of the line breaks.
zapata.conf
ukcallerid=yes
callerid=asreceived
signalling=fxs_ks
channel = 1 : BT line
channel = 2 : Telewest line
I also have immediate=yes, but that shouldn't affect
Tony -
This sounds great. Are you monitoring the line constantly for the
inbound caller ID or are you somehow detecting the polarity reversal?
Look forward to trying out your solution! I think you will have a lot
of happy bunnies here in Blighty, as the current lack of caller ID on
our BT
Tim Robinson wrote:
Tony -
This sounds great. Are you monitoring the line constantly for the
inbound caller ID or are you somehow detecting the polarity reversal?
I keep rolling buffer of the last couple of seconds of the incoming
audio, so when the ring is detected the chan_zap driver can grab
: [Asterisk-Users] Caller ID with BT CD50
Tim Robinson wrote:
Tony -
This sounds great. Are you monitoring the line constantly for the
inbound caller ID or are you somehow detecting the polarity reversal?
I keep rolling buffer of the last couple of seconds of the incoming
audio, so when the ring
-Users] Caller ID with BT CD50
Tim Robinson wrote:
Tony -
This sounds great. Are you monitoring the line constantly for the
inbound caller ID or are you somehow detecting the polarity reversal?
I keep rolling buffer of the last couple of seconds of the incoming
audio, so when the ring
David J Carter wrote:
Tony,
Lost some of the mails on this topic somewhere.
Does this need the BT50 mod or will the X100p now output the Caller ID?
It's to allow the X100P to output the caller ID.
My soldering skills just weren't up to the BT50 mod :)
Tony
--
All your code belongs to Santa
Tony
Robinson Tim-W10277 wrote:
Presumably this can then be modified for DTMF caller ID by those in NL, Brazil etc?
I will give it a go soon.
I'd expect so. The zaptel mod just lets you grab what happened just
before the ring... processing it is a relatively simple addition (no
idea how you'd do
Tony,
The patches work great, picks up the BT callerid everytime.
A really big thankyou!
Chris
- Original Message -
From: Tony Hoyle [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 2:09 PM
Subject: Re: [Asterisk-Users] Caller ID with BT CD50
David J Carter
Chris Stenton wrote:
Tony,
The patches work great, picks up the BT callerid everytime.
A really big thankyou!
A big THANK YOU from me too!!!
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
Tony,
Are you going to submit the patches to the cvs head?
Chris
- Original Message -
From: Kevin Walsh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 4:15 PM
Subject: RE: [Asterisk-Users] Caller ID with BT CD50
Tony Hoyle [EMAIL PROTECTED] wrote:
Lost
Can confirm it works with Generic X101P
*BIG* Thank you :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin Walsh
Sent: 26 May 2004 16:15
To: [EMAIL PROTECTED]
Subject: RE: [Asterisk-Users] Caller ID with BT CD50
Tony Hoyle [EMAIL PROTECTED] wrote
Chris Stenton wrote:
Tony,
Are you going to submit the patches to the cvs head?
http://bugs.digium.com/bug_view_page.php?bug_id=0001719
Tony
--
All your code belongs to Santa
Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13
Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B
Chris Stenton [EMAIL PROTECTED] wrote:
Tony,
Are you going to submit the patches to the cvs head?
He has published his patches, but probably doesn't have commit access
to the Asterisk CVS archive (correct me if I'm wrong).
The people who do have CVS commit access can pick up the published
On Wednesday 26 May 2004 17:07, Karl Dyson wrote:
Can confirm it works with Generic X101P
*BIG* Thank you :)
I can confirm it works with my generic X100P (at least I think that's what it
is :) ).
The full callerID is put into my database, so I know it's receiving the
complete CID. The phone
The full callerID is put into my database, so I know it's receiving the
complete CID. The phone only seems to get sent the first 8 digit's - I'm
sure this is something in my configs, but I've not had chance to look into
it yet.
It looks like my missing digit problems are down to the dect
Amaury Jacquot wrote:
Tony Hoyle wrote:
Guess what... BT actually charge a monthly rental fee (£1.50 or ~$2.40
per month) for providing this information. Gotta love state
monopolies hmm? Hope they don't take too long provisioning it...
heh, they'll probably mess up some other setting on that
Tony Hoyle wrote:
The CID specs look really simple... I'll definately have a go at
implementing something like it. Just need to find a spec sheet for the
Intel chipset in the FX100/FX101 (to see if you somehow see the pulse
that comes just before the ring - I always wondered why phones tended
Tony Hoyle wrote:
Guess what... BT actually charge a monthly rental fee (£1.50 or ~$2.40
per month) for providing this information. Gotta love state monopolies
hmm? Hope they don't take too long provisioning it...
heh, they'll probably mess up some other setting on that line, or mess
up your
: Re: [Asterisk-Users] Caller ID with BT CD50
Karl Dyson wrote:
Hi All,
Having searched the archives, I can see there has been much
discussion
at various points regarding capture of caller id information from
good
old BT.
If I understand correctly, it seems that not only do
Karl Dyson wrote:
Well, I have a USR015630B, which, according to the FAQ supports (UK)
CLI. It supports the at #cli command, but no matter what I try, it will
not pick up the caller id. Lucky I already had it and didn't buy it
soley for this purpose! My caller display unit (unfortunately a CD60 --
I have a USR modem too but it's a brick unfortunately... Pity as it
was
a nice modem... the right model too so it might have worked.
I wonder what it would take to get the zaptel drivers to pick up CID
(or
even a cheap conexxant modem or something like that) - these soft
modems
are pretty
On Sun, 23 May 2004, Karl Dyson wrote:
Of course, although my wife is happy with the Cisco 7905s that have
sprung up around the house, she still likes the cordless DECT units we
have, and so they're plugged into an ATA186. Problem is, they no longer
display caller id due to the ATA186 not
Karl Dyson wrote:
Of course, although my wife is happy with the Cisco 7905s that have
sprung up around the house, she still likes the cordless DECT units we
have, and so they're plugged into an ATA186. Problem is, they no longer
display caller id due to the ATA186 not poking it out in BT format I
ATA186 firmware 3.0+ supports more formats.
Certainly with 3.0 my BT DECT 3010 (rebadged Siemens) base copes fine.
Oooh Now which setting would I need to check?? I have a Philips Onis
DECT system, which does CLI quite happily on the BT line, and I just
checked the ATA and its running :
On Sun, 23 May 2004, gARetH baBB wrote:
On Sun, 23 May 2004, Karl Dyson wrote:
Of course, although my wife is happy with the Cisco 7905s that have
sprung up around the house, she still likes the cordless DECT units we
have, and so they're plugged into an ATA186. Problem is, they no
If you had CID to start with, I'd expect it to work - eg. you wouldn't
get
it
from the POTS line but if a VOIP call came in and the ATA186
retransmitted
that in US format then a US handset would pick it up.
But once I can get the cid working, I'm hoping I can persuade the DECT
units to pick
On Sun, 23 May 2004, Karl Dyson wrote:
Oooh Now which setting would I need to check?? I have a Philips Onis
DECT system, which does CLI quite happily on the BT line, and I just
checked the ATA and its running :
http://www.cisco.com/en/US/products/hw/gatecont/ps514/products_administr
at
ion_guide_chapter09186a00801e0eb0.html#wp1113416
ETSI method (type 2).
I know my CD50 still doesn't like this method, but then as the first
generation device it can be *very* fussy at the best of times -
indeed,
Karl Dyson wrote:
Hi All,
Having searched the archives, I can see there has been much discussion
at various points regarding capture of caller id information from good
old BT.
If I understand correctly, it seems that not only do the drivers not
currently support it, but my X101P
55 matches
Mail list logo
