> I got a call from an overseas call center telling me about the
> problems with the Windows machine I was using. They wanted to remote
> in and fix things for me ... (Ignore the fact I use a MacBook Pro or
> an ASUS laptop with Debian).
>
> What I found curious was the caller's name was Asterisk,
Am 26.08.2014 16:45, schrieb Jeffrey Walton:
I got a call from an overseas call center telling me about the
problems with the Windows machine I was using. They wanted to remote
in and fix things for me ... (Ignore the fact I use a MacBook Pro or
an ASUS laptop with Debian).
This is a common sca
On 08/26/2014 09:55 AM, Doug Lytle wrote:
What I found curious was the caller's name was Asterisk
On our systems, if I don't assign a CID number to an inbound call that is
blocking it's CID, the default shown on the Polycom phones is Asterisk. I've
set it up that any inbound call with no CID
>> What I found curious was the caller's name was Asterisk
On our systems, if I don't assign a CID number to an inbound call that is
blocking it's CID, the default shown on the Polycom phones is Asterisk. I've
set it up that any inbound call with no CID is assigned a 0 for the phone
number and
Asterisk can set any Caller ID name and number you want with the CALLERID()
function.
Type 'core show function CALLERID()' on the Asterisk command line to get
the details.
Whether your trunk will convey the Caller ID you have set is another matter
- and entirely the choice of your outbound carrie
I got a call from an overseas call center telling me about the
problems with the Windows machine I was using. They wanted to remote
in and fix things for me ... (Ignore the fact I use a MacBook Pro or
an ASUS laptop with Debian).
What I found curious was the caller's name was Asterisk, and the
cal