For outgoing calls made on our PRI circuit we are setting the Caller ID
using the format
Exten => _9XXXXXXX,1,SetCallerID(1601XXXXXXX)
The monitor shows that the CallerID is being set to the specified
number, but yet when the call is received on the user end the ID is
always the base number of our DID. For example we have 8600-8650 as
DID's but the callerid is always 8600 regardless of the extension that
makes the outgoing call.
We have tried using the variable SetCallerID(${BYEXTENSION}) but still
get the same results.
Any suggestions?
JP McInnis, Director of Technology
Copiah Lincoln Community College
Regardless of what you send in callerid, your PRI has a phone number associated with it that you don't see, but is used for billing. This is so you cannot spoof the LD company into thinking the call came from somewhere other than from you. I believe the PRI provider can provision the PRI to use either this "hard-wired" callerid , or the one you provide. It sounds to me like your PRI is provisioned as the former. I would talk to your PRI provider and see if they agree and are willing to change this. Bruce Komito High Sierra Networks, Inc. www.servers-r-us.com (775) 236-5815 On Tue, 29 Jun 2004, McInnis, JP wrote:> > For outgoing calls made on our PRI circuit we are setting the Caller ID > using the format > > Exten => _9XXXXXXX,1,SetCallerID(1601XXXXXXX) > > The monitor shows that the CallerID is being set to the specified > number, but yet when the call is received on the user end the ID is > always the base number of our DID. For example we have 8600-8650 as > DID's but the callerid is always 8600 regardless of the extension that > makes the outgoing call. > > We have tried using the variable SetCallerID(${BYEXTENSION}) but still > get the same results. > > Any suggestions? > > > JP McInnis, Director of Technology > Copiah Lincoln Community College > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
On Tuesday 29 June 2004 10:13, McInnis, JP wrote:> The monitor shows that the CallerID is being set to the specified > number, but yet when the call is received on the user end the ID is > always the base number of our DID. For example we have 8600-8650 as > DID's but the callerid is always 8600 regardless of the extension that > makes the outgoing call.Your telco is restricting your outgoing caller ID. I'd contact your sales rep, as this is something only the telco can fix. -A.
Drop the leading 1 On Tue, 2004-06-29 at 09:13, McInnis, JP wrote:> For outgoing calls made on our PRI circuit we are setting the Caller ID > using the format > > Exten => _9XXXXXXX,1,SetCallerID(1601XXXXXXX) > > The monitor shows that the CallerID is being set to the specified > number, but yet when the call is received on the user end the ID is > always the base number of our DID. For example we have 8600-8650 as > DID's but the callerid is always 8600 regardless of the extension that > makes the outgoing call. > > We have tried using the variable SetCallerID(${BYEXTENSION}) but still > get the same results. > > Any suggestions? > > > JP McInnis, Director of Technology > Copiah Lincoln Community College > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users-- Eric Wieling * BTEL Consulting * 504-899-1387 x2111 "In a related story, the IRS has recently ruled that the cost of Windows upgrades can NOT be deducted as a gambling loss."
Robinson Tim-W10277
2004-Jun-29 07:45 UTC
[Asterisk-Users] Outgoing CallerID on PRI problems
Some telcos require you only to send a certain number of digits. Try
sending fewer and fewer digits and see if it starts working. E.g.
instead of sending 1601abcdefg try sending 601abcdefg or abcdefg or defg
or even fg
If this doesn't work, from the CLI type pri debug span x and see what
you get in the SETUP message.
Other possiblities are in zapata.conf - you may need to set the correct
parameters for your type of PRI. Best thing might be to ask your telco
how your line is configured.
Please report back with success/failure. We all like to hear of
people's successes as well as problems!
Rgds
Tim
-----Original Message-----
From: asterisk-users-admin@lists.digium.com
[mailto:asterisk-users-admin@lists.digium.com] On Behalf Of McInnis, JP
Sent: 29 June 2004 15:13
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] Outgoing CallerID on PRI problems
For outgoing calls made on our PRI circuit we are setting the Caller ID
using the format
Exten => _9XXXXXXX,1,SetCallerID(1601XXXXXXX)
The monitor shows that the CallerID is being set to the specified
number, but yet when the call is received on the user end the ID is
always the base number of our DID. For example we have 8600-8650 as
DID's but the callerid is always 8600 regardless of the extension that
makes the outgoing call.
We have tried using the variable SetCallerID(${BYEXTENSION}) but still
get the same results.
Any suggestions?
JP McInnis, Director of Technology
Copiah Lincoln Community College
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
On 29/06/04 15:13, McInnis, JP wrote:> The monitor shows that the CallerID is being set to the specified > number, but yet when the call is received on the user end the ID is > always the base number of our DID. [...]There are many things to try that others haven't touched on. - Make sure your pridialplan setting is correct for both dialled *and* presented number. - Make sure you're sending the right number of digits. You can ask your telco how many to send if they're clueful and you can find the right techie to talk to. - Some things are misleading. For example, we discovered we could set our presentation TON (pridialplan) to be international, and that this would work for most lines, but that for for some calls routed over least-cost routing to mobile operators and the like the caller ID wasn't appearing on the remote party's 'phone. We discovered that the telco only properly supports the TON being national on their switch. One of our telcos requires a different pridialplan (type of number, or TON) for the presented number than for the dialled number, which Asterisk doesn't natively support. We realised this must be the case because we tried everything else and when you do a "pri debug span x" (where x should be replaced by a span number, obviously) in the call setup it keeps claiming you have an invalid number being presented (I don't have the precise log to hand, I'm afraid). If you discover this is the case, e-mail me and I can send you a patch. I ought to get around to adding a bug report/feature request about that, too. :) You may also want to check out the Callingpres() app. For example, to hide caller ID on many PRI switches, first you have to set it to something, then you have to specify that you want it hidden. Otherwise Asterisk doesn't know what TON to set (because there isn't a number), so it sets the TON to unknown (0), and it doesn't work: [dialZapHideCli] exten => _X.,1,SetCallerID(1234567890) exten => _X.,2,Callingpres(35) exten => _X.,3,Dial(Zap/g1/${EXTEN}) Regards, Alastair -- Alastair Maw Systems Analyst http://www.mxtelecom.com