| View previous topic :: View next topic |
| Author |
Message |
lotusscript at gmail.com
Guest
|
 Posted: Fri Apr 25, 2008 6:55 am Post subject: [asterisk-users] Upgrading to 1.4 |
 |
|
A good while back when installing 1.2 there were major issues with UK
callerid. Asterisk 1.2 didn't recognise the callerid correctly because
of the way BT sent the information. Sometimes before the first ring or
just after. After applying a third party patch we got it to work. We
were afraid to touch it after that  Has this problem now gone away
with 1.4? |
|
| Back to top |
|
 |
lotusscript at gmail.com
Guest
|
| Posted: Fri Apr 25, 2008 9:58 am Post subject: [asterisk-users] Upgrading to 1.4 |
|
|
A good while back when installing 1.2 there were major issues with UK
callerid. Asterisk 1.2 didn't recognise the callerid correctly because
of the way BT sent the information. Sometimes before the first ring or
just after. After applying a third party patch we got it to work. We
were afraid to touch it after that Has this problem now gone away
with 1.4? |
|
| Back to top |
|
|
gordon+asterisk at dro...
Guest
|
| Posted: Sat Apr 26, 2008 2:56 am Post subject: [asterisk-users] Upgrading to 1.4 |
|
|
On Sat, 26 Apr 2008, Rob Hillis wrote:
| Quote: | As is just about always the case, posting twice to the list within three
hours is not only unlikely to get a faster response, I would in fact imagine
it would /reduce/ your chances of getting a response at all.
|
I suspect he didn't. I've seen many instances here where posts appear
twice (or more). In my own experience of running mailling lists over the
years, I've found this is often caused by some broken Exchnge server
somewhere....
| Quote: | lotusscript wrote:
| Quote: | A good while back when installing 1.2 there were major issues with UK
callerid. Asterisk 1.2 didn't recognise the callerid correctly because
of the way BT sent the information. Sometimes before the first ring or
just after. After applying a third party patch we got it to work. We
were afraid to touch it after that Has this problem now gone away
with 1.4?
|
|
No idea about this though - I had the same issues, but have stuck to 1.2
for the time being.
(And from what I recall, it was nothing to do with the way BT sent the
information, but the wctdm driver simply being "broke" until the patch
fixed it)
Gordon |
|
| Back to top |
|
|
matt at mbrown.co.uk
Guest
|
| Posted: Sat Apr 26, 2008 4:03 am Post subject: [asterisk-users] Upgrading to 1.4 |
|
|
On 25 Apr 2008, at 15:58, lotusscript wrote:
| Quote: | A good while back when installing 1.2 there were major issues with UK
callerid. Asterisk 1.2 didn't recognise the callerid correctly
because
of the way BT sent the information. Sometimes before the first ring
or
just after. After applying a third party patch we got it to work. We
were afraid to touch it after that Has this problem now gone
away
with 1.4?
|
I run Asterisk 1.4.19 with Zaptel 1.4.10 on Ubuntu with a TDM400P -
and still having issues with Callerid and Distinctive Ring.
The only way I have managed to get callerid to work with success is to
patch the Zaptel source in 1.4.5.1 - however distinctive ring is
broken - but this appears to be a Chan_Zap issue rather than Zaptel.
Regards
Matt |
|
| Back to top |
|
|
lotusscript at gmail.com
Guest
|
| Posted: Mon Apr 28, 2008 7:17 am Post subject: [asterisk-users] Upgrading to 1.4 |
|
|
A good while back when installing 1.2 there were major issues with UK
callerid. Asterisk 1.2 didn't recognise the callerid correctly because
of the way BT sent the information. Sometimes before the first ring or
just after. After applying a third party patch we got it to work. We
were afraid to touch it after that Has this problem now gone away
with 1.4? |
|
| Back to top |
|
|
phil-asterisk at tinsl...
Guest
|
| Posted: Mon Apr 28, 2008 7:33 am Post subject: [asterisk-users] Upgrading to 1.4 |
|
|
On Mon, Apr 28, 2008 at 01:17:33PM +0100, lotusscript wrote:
| Quote: |
A good while back when installing 1.2 there were major issues with UK
callerid. Asterisk 1.2 didn't recognise the callerid correctly because
of the way BT sent the information. Sometimes before the first ring or
just after. After applying a third party patch we got it to work. We
were afraid to touch it after that Has this problem now gone away
with 1.4?
|
I am on an unpatched 1.2 and BT caller ID works fine for me. However,
that is not to say there may be peculiar practice elsewhere.
What won't work is distinctive ring detection and caller ID together.
--
Phil Reynolds
o ____ mail: phil-asterisk at tinsleyviaduct.com
|L_ \ / Web: http://www.tinsleyviaduct.com/phil/
(_)- \/ Waltham 66, Emley Moor 69, Droitwich 79, Windows 95 |
|
| Back to top |
|
|
|
Search
