Ascendis Caller ID in sip environment?
Posted: Tue Feb 24, 2009 7:52 am
Hello:
I bought Ascendis Caller ID in June of 2006 and love it. However, I can no longer use it, due to a change in the
infrastructure of my phone system, and have had a license hanging around for a couple of years with nothing much to do.
When I originally registered Ascendis Caller ID, I had Vonage with it's supplied analog telephone adapter (ATA), and was
running the software on an old 600mhz Compaq Deskpro, with an ancient U.S. Robotics 33.6 isa voice modem, because it was the
only modem in the house that supported CID type 1.
Now, however, I no longer have any analog connections. My phone system is running on a remote Asterisk server in a datacenter
in Atlanta, and all the phones in the house are non-analog sip phones, I.E. Snom 320 and m3, Polycom IP-320, Grandstream
BT101, various softphones when needed, and the sip client on my Nokia e71 smartphone.
I also have a Zoom 5801 ATA, but this is not on any of my personal extensions, so I can't use it to send information to
Ascendis from any of my DIDs, or calls from local extensions on my system, or from remotely connected PBXs of which I am a
part.
I realize I could buy a two FXS port ATA and register another extension on the PBX just for Ascendis, but I know the
technology exists to take an unnecessary modem out of the equation.
I searched around for similar server/client methods of blasting CID info from my Asterisk box to multiple Windows machines in
the house. I found a tapi driver for Windows, called siptapi, which would replace the modem with a sip stack with credentials
that I could then implement in my Asterisk dial plan, which looked promising. However, it doesn't support incoming call
notification, unless you buy the highly expensive ?1000 commercial license.
I should also mention that I am blind, and there were many other solutions that might have done the trick, but were either
incredibly hard/inconvenient for my assistive technology to read, or never quite did the job in the first place.
The only solution I found that actually worked for me, with very minimal configuration on my part, though it was much simpler
than Ascendis Caller ID, was Yac (http://sunflowerhead.com/software/yac/) and a script that uses gnu netcat to echo incoming
CID info to a specific TCP address and port, which was then received by a client on a windows machine, logged to a text file,
and displayed as a tool tip.
More information can be found here:
http://www.voip-info.org/wiki/view/Aste ... tification
At the time, my PBX was local, and I could simply include all the internal IPs to which I wished to send CID info, but now my
phone system is remote, and it's harder, less practical, though not impossible to do with the current configuration.
To put it lightly, I'd much rather use Ascendis Caller ID with one local server that connects to the phone system, rather
than dealing with multiple ports, or possibly even multiple public IP addresses, which is really not necessary, or fun, for
that matter.
I'm wondering if it is possible to:
1. have Ascendis Caller ID server emulate a yac client in place of a modem, so that any yac compatible application can send properly
formatted data to Ascendis Caller ID for further processing. Apparently, the YAC protocol specifications are pretty easy to implement.
2. emulate a whozz calling? Ethernet device that connects to Asterisk, or have Asterisk itself emulate such a device, which
Ascendis Caller ID can then use.
or
3. deploy a similar concept as siptapi (http://www.ipcom.at/index.php?id=561) that actually works, I.E. create an extension
on the PBX which forwards to Ascendis Caller ID via a virtual modem, and does nothing other than send CID and ring, although, given this method,
all calls would probably show up as "missed".
I'd really like to be able to use Ascendis Caller ID in an all-sip environment, and really miss the convenient interface for
retrieving caller information.
I read somewhere that Ascendis Caller ID would eventually include sip support, and that it was in a beta release, but then
was later removed. What's the status on that, and what was it's intended use?
P.S. No, I am not an I.T. professional, justt an end-user who was bored with conventional telecommunications.
I bought Ascendis Caller ID in June of 2006 and love it. However, I can no longer use it, due to a change in the
infrastructure of my phone system, and have had a license hanging around for a couple of years with nothing much to do.
When I originally registered Ascendis Caller ID, I had Vonage with it's supplied analog telephone adapter (ATA), and was
running the software on an old 600mhz Compaq Deskpro, with an ancient U.S. Robotics 33.6 isa voice modem, because it was the
only modem in the house that supported CID type 1.
Now, however, I no longer have any analog connections. My phone system is running on a remote Asterisk server in a datacenter
in Atlanta, and all the phones in the house are non-analog sip phones, I.E. Snom 320 and m3, Polycom IP-320, Grandstream
BT101, various softphones when needed, and the sip client on my Nokia e71 smartphone.
I also have a Zoom 5801 ATA, but this is not on any of my personal extensions, so I can't use it to send information to
Ascendis from any of my DIDs, or calls from local extensions on my system, or from remotely connected PBXs of which I am a
part.
I realize I could buy a two FXS port ATA and register another extension on the PBX just for Ascendis, but I know the
technology exists to take an unnecessary modem out of the equation.
I searched around for similar server/client methods of blasting CID info from my Asterisk box to multiple Windows machines in
the house. I found a tapi driver for Windows, called siptapi, which would replace the modem with a sip stack with credentials
that I could then implement in my Asterisk dial plan, which looked promising. However, it doesn't support incoming call
notification, unless you buy the highly expensive ?1000 commercial license.
I should also mention that I am blind, and there were many other solutions that might have done the trick, but were either
incredibly hard/inconvenient for my assistive technology to read, or never quite did the job in the first place.
The only solution I found that actually worked for me, with very minimal configuration on my part, though it was much simpler
than Ascendis Caller ID, was Yac (http://sunflowerhead.com/software/yac/) and a script that uses gnu netcat to echo incoming
CID info to a specific TCP address and port, which was then received by a client on a windows machine, logged to a text file,
and displayed as a tool tip.
More information can be found here:
http://www.voip-info.org/wiki/view/Aste ... tification
At the time, my PBX was local, and I could simply include all the internal IPs to which I wished to send CID info, but now my
phone system is remote, and it's harder, less practical, though not impossible to do with the current configuration.
To put it lightly, I'd much rather use Ascendis Caller ID with one local server that connects to the phone system, rather
than dealing with multiple ports, or possibly even multiple public IP addresses, which is really not necessary, or fun, for
that matter.
I'm wondering if it is possible to:
1. have Ascendis Caller ID server emulate a yac client in place of a modem, so that any yac compatible application can send properly
formatted data to Ascendis Caller ID for further processing. Apparently, the YAC protocol specifications are pretty easy to implement.
2. emulate a whozz calling? Ethernet device that connects to Asterisk, or have Asterisk itself emulate such a device, which
Ascendis Caller ID can then use.
or
3. deploy a similar concept as siptapi (http://www.ipcom.at/index.php?id=561) that actually works, I.E. create an extension
on the PBX which forwards to Ascendis Caller ID via a virtual modem, and does nothing other than send CID and ring, although, given this method,
all calls would probably show up as "missed".
I'd really like to be able to use Ascendis Caller ID in an all-sip environment, and really miss the convenient interface for
retrieving caller information.
I read somewhere that Ascendis Caller ID would eventually include sip support, and that it was in a beta release, but then
was later removed. What's the status on that, and what was it's intended use?
P.S. No, I am not an I.T. professional, justt an end-user who was bored with conventional telecommunications.