Justin,
I'm pretty sure that AAH does the SetCallerID for you.
I'll tell you what I do when I want to test some things with AAH/Trixbox.
I edit extensions_custom.conf and add whatever I want to
[from-internal-custom]. (At least, I'm pretty sure that's what it's
called, I'm not sitting at a box right now)
In this case, I just made a few entries like this:
exten => _8NXXNXXXXXX,1,noop(Using outgoing test extension)
exten => _8NXXNXXXXXX,2,SetCallerID("Dave" <4165551212>)
exten => _8NXXNXXXXXX,3,Dial(Zap/g0/${EXTEN:1})
exten => _8NXXNXXXXXX,4,Hangup()
That way, instead of dialing my usual 9+number for local calls, I can
dial 8+number and it uses my alternate logic. That way, I'm not
interfering with normal operation on the switch and I don't have to
tamper with the AAH code. I did exactly this when I saw Simon's post
to see if it helped my situation. Sadly, it didn't.
I'm glad to hear that your PRI works transmitting callerID. So,
you're having problems with caller name on SIP? Have you tried doing
"SIP DEBUG" at the CLI. It's a lot of information to sift through,
and you don't have to understand all of it, but you should be able to
see where it sends the caller name and number. Then at least you'll
know whether you're sending it to your provider.
As I'm sure you've figured out, some SIP providers, (like PRI
providers) won't let you arbitrarily set your calling name.
Let me know how you make out. I've worked a little bit with AAH so I
might be able to help out a bit.
Dave
On 7/26/06, Justin Sweeney <[EMAIL PROTECTED]> wrote:
Hi Dave;
I do have a Bell PRI that is passing the CID ok. Sorry I haven't as of yet
been able to post my config. Set up. It has been a while since I've poked
around in my Asterisk server. I will get something posted later this week or
early next.
P.S.
I got the recommendation from Simon:
Use the SetCallerID application to change both the name and number, it may
work:
exten => 100,1,SetCallerID("John Smith" <4165551212>)
But since I mainly use the [EMAIL PROTECTED] GUI interface so I am having some
trouble making this change to my extensions.conf file.
Justin
-----Original Message-----
From: Dave Donovan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 26, 2006 1:20 PM
To: [email protected]
Subject: Re: [on-asterisk] RE: name and caller ID
Justin,
Any luck with sending calling name at your end?
Here's what I've found so far.
My carrier sees the name I send in his debug. He's not using it for Calling
Name because it's coming in a 'display' field and not in a 'facility info
element' (sometimes called facility IE). He wants me to send it as Facility
IE, not as display.
Some googling shows that there is work going on in this area. There seem to
be some examples of a 'facilityenable' in zapata.conf but it doesn't seem to
be supported at my version of libpri and/or zaptel.
I'll look at upgrading.
I'll do some more looking and keep you all posted.
The new information here is: It's possible for asterisk to transmit Calling
Name to a carrier who is willing to honour it, but it's not propogated
because it's coming in the wrong ISDN field.
BTW: Thanks to everyone for their informative posts.
Dave Donovan
On 7/24/06, Justin Sweeney <[EMAIL PROTECTED]> wrote:
>
>
> Hi;
>
> Does anyone knoe how to easily include a caller 'name' ID on SIP accounts?
>
> I have a PRI (with DID's) which is working great and passing the
> caller ID number perfectly; but I want to include the 'name' so that
> it also shows up when I call a Bell Landline or homeline etc.
>
> Justin
--
David Donovan
Consultant
Fulcrum Solutions
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,
e-mail: [EMAIL PROTECTED]
--
David Donovan
Consultant
Fulcrum Solutions
