Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-14 Thread Jon Moore
Update on my problem.

After a few days of speaking with various folks at ATT, the issue has
been resolved.  When we first ordered our PRI lines, they were
supposed to be without screening tables (per ATT suggestion on how we
can set CID numbers to numbers not associated with the PRI).  However,
this was apparently never done.

So, asterisk is working just fine.  My setting of the callerid is
working just as it should.  ATT is just blocking the number I send,
and instead sending the main billing number on the PRI lines.

-jonathan

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Jon Moore
Hi list.  I've googled around for this, and so far have come up short.

I'm attempting to set the outbound callerid when making a call using
our PRI.  I've talked with ATT (the providor) and they have said the
screening table has been disabled, so anything my phone system sends
for callerid should be passing along.  However, when I make a call,
the primary number assigned on our PRI is showing up, not the value
I've set.

Here is how I'm making the call...

exten = _91NXXNXX,1,Set(CALLERID(all)=Corner Homecare 12703653903)
exten = _91NXXNXX,2,Dial(DAHDI/G2/${EXTEN:1}})

I'll be glad to offer up any debugging information that you might
need, if it will help. I'm using Asterisk 1.6.0.14 and DAHDI 2.2.0.

TIA

-jonathan

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Klaus Darilion
use pri debugging (pri debug span 1) to verify if the data sent on the 
PRI line is correct! (e.g. type on number, ...)

verify with an incoming call and set the same format on outgoing calls.

regards
klaus

Jon Moore schrieb:
 Hi list.  I've googled around for this, and so far have come up short.
 
 I'm attempting to set the outbound callerid when making a call using
 our PRI.  I've talked with ATT (the providor) and they have said the
 screening table has been disabled, so anything my phone system sends
 for callerid should be passing along.  However, when I make a call,
 the primary number assigned on our PRI is showing up, not the value
 I've set.
 
 Here is how I'm making the call...
 
 exten = _91NXXNXX,1,Set(CALLERID(all)=Corner Homecare 12703653903)
 exten = _91NXXNXX,2,Dial(DAHDI/G2/${EXTEN:1}})
 
 I'll be glad to offer up any debugging information that you might
 need, if it will help. I'm using Asterisk 1.6.0.14 and DAHDI 2.2.0.
 
 TIA
 
 -jonathan
 
 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 
 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Jon Moore
On Tue, Nov 10, 2009 at 10:39 AM, Klaus Darilion
klaus.mailingli...@pernau.at wrote:
 use pri debugging (pri debug span 1) to verify if the data sent on the
 PRI line is correct! (e.g. type on number, ...)

 verify with an incoming call and set the same format on outgoing calls.

This is what I see on an incomming call (hopefully, this is right part
of the pri debug

 Calling Number (len=14) [ Ext: 0  TON: National Number (2)  NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
   Presentation: Presentation allowed of
network provided number (3)  '8124307660' ]

And on my outgoing call..

 Calling Number (len=15) [ Ext: 0  TON: National Number (2)  NPI: 
 ISDN/Telephony Numbering Plan (E.164/E.163) (1)
   Presentation: Presentation permitted, user number 
 not screened (0)  '2703653903' ]

I changed the line in extensions.conf to be SET(CALLERID(ALL)=Corner
Homecare 2703653903)
To match what it appears I'm getting from ATT, only the 10 digit number.

Not sure if it's relevant here, but in /etc/asterisk/chan_dahdi.conf I
have the following:

 pridialplan=unknown
 prilocaldialplan=national


-jonathan

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Doug Lytle
Jon Moore wrote:
 I changed the line in extensions.conf to be SET(CALLERID(ALL)=Corner
 Homecare2703653903)
 To match what it appears I'm getting from ATT, only the 10 digit number.


We've got ATT out of the Detroit area, you can't set callerid name, 
only number.  So, try:

exten = _91NXXNXX,1,Set(CALLERID(number)=12703653903)

Doug


-- 

Ben Franklin quote:

Those who would give up Essential Liberty to purchase a little Temporary 
Safety, deserve neither Liberty nor Safety.


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Jon Moore
On Tue, Nov 10, 2009 at 11:43 AM, Doug Lytle supp...@drdos.info wrote:
 Jon Moore wrote:
 I changed the line in extensions.conf to be SET(CALLERID(ALL)=Corner
 Homecare2703653903)
 To match what it appears I'm getting from ATT, only the 10 digit number.


 We've got ATT out of the Detroit area, you can't set callerid name,
 only number.  So, try:

 exten = _91NXXNXX,1,Set(CALLERID(number)=12703653903)

I noticed I had the number wrapped in angle brackets here, and removed
those as well. Still having the issue though.
Thanks for the pointer.

Did you have to provide ATT with a list of numbers you would be
setting, or does it Just Work?

-jonathan

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Danny Nicholas
If all else fails, there's always spoofing.

-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Jon Moore
Sent: Tuesday, November 10, 2009 12:09 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Setting outgoing callerid on when using a PRI

On Tue, Nov 10, 2009 at 11:43 AM, Doug Lytle supp...@drdos.info wrote:
 Jon Moore wrote:
 I changed the line in extensions.conf to be SET(CALLERID(ALL)=Corner
 Homecare2703653903)
 To match what it appears I'm getting from ATT, only the 10 digit number.


 We've got ATT out of the Detroit area, you can't set callerid name,
 only number.  So, try:

 exten = _91NXXNXX,1,Set(CALLERID(number)=12703653903)

I noticed I had the number wrapped in angle brackets here, and removed
those as well. Still having the issue though.
Thanks for the pointer.

Did you have to provide ATT with a list of numbers you would be
setting, or does it Just Work?

-jonathan

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Doug Lytle
Jon Moore wrote:

 Did you have to provide ATT with a list of numbers you would be
 setting, or does it Just Work?



In our Detroit and Indianpolis installs, it just worked.  In our Battle 
Creek installs, we can only set the numbers to DIDs that we directly own.

Doug

-- 

Ben Franklin quote:

Those who would give up Essential Liberty to purchase a little Temporary 
Safety, deserve neither Liberty nor Safety.


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Doug Lytle
Jon Moore wrote:
 On Tue, Nov 10, 2009 at 11:43 AM, Doug Lytlesupp...@drdos.info  wrote:

 Jon Moore wrote:
  


Here is what I have in our zaptel.conf

span=1,1,0,esf,b8zs
defaultzone=us
loadzone=us
bchan=1-23
dchan=24

And our zapata.conf:

switchtype=national
context=pri
signalling=pri_cpe
group=1
echocancel=yes
echotraining=yes
echocancelwhenbridged=yes
rxgain=-1.0
txgain=-4.0
busydetect=no
callprogress=no
pridialplan=unknown
usercallerid=yes
callerid=asreceived
channel = 1-23

Doug

-- 

Ben Franklin quote:

Those who would give up Essential Liberty to purchase a little Temporary 
Safety, deserve neither Liberty nor Safety.


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Danny Nicholas
Name is controlled by Telco; you publish new number and Telco will provide
name or unknown based on new number.

-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Doug Lytle
Sent: Tuesday, November 10, 2009 11:43 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Setting outgoing callerid on when using a PRI

Jon Moore wrote:
 I changed the line in extensions.conf to be SET(CALLERID(ALL)=Corner
 Homecare2703653903)
 To match what it appears I'm getting from ATT, only the 10 digit number.


We've got ATT out of the Detroit area, you can't set callerid name, 
only number.  So, try:

exten = _91NXXNXX,1,Set(CALLERID(number)=12703653903)

Doug


-- 

Ben Franklin quote:

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety.


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Dave Fullerton
Jon Moore wrote:
 On Tue, Nov 10, 2009 at 11:43 AM, Doug Lytle supp...@drdos.info wrote:
 Jon Moore wrote:
 I changed the line in extensions.conf to be SET(CALLERID(ALL)=Corner
 Homecare2703653903)
 To match what it appears I'm getting from ATT, only the 10 digit number.

 We've got ATT out of the Detroit area, you can't set callerid name,
 only number.  So, try:

 exten = _91NXXNXX,1,Set(CALLERID(number)=12703653903)
 
 I noticed I had the number wrapped in angle brackets here, and removed
 those as well. Still having the issue though.
 Thanks for the pointer.
 
 Did you have to provide ATT with a list of numbers you would be
 setting, or does it Just Work?
 
 -jonathan

I have an ATT PRI out of Holland and it just works. I actually have 
it pass the internal extension number as outbound called ID (which is 4 
digits) when anyone calls my cell phone so I know how to answer and it 
works fine.

This is what I'm using:
  set(CALLERID(num)=1234567890)

Note num and not number I don't know if that was a change from 1.4 
to 1.6 or if Doug mistyped it.


-Dave

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Doug Lytle
Dave Fullerton wrote:

 Note num and not number I don't know if that was a change from 1.4
 to 1.6 or if Doug mistyped it.


Not a mistype.  I've been using number all along, but looking at the 
docs shows that I've been incorrect.  It must concatenate the number 
down to num.  Looks like I've got a little modifying to do this evening:


core show function CALLERID
livonia*CLI
   -= Info about function 'CALLERID' =-

[Syntax]
CALLERID(datatype[,optional-CID])

[Synopsis]
Gets or sets Caller*ID data on the channel.

[Description]
Gets or sets Caller*ID data on the channel.  The allowable datatypes
are all, name, *num*, ANI, DNID, RDNIS.
Uses channel callerid by default or optional callerid, if specified.

Doug

-- 

Ben Franklin quote:

Those who would give up Essential Liberty to purchase a little Temporary 
Safety, deserve neither Liberty nor Safety.


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Jason Parker
Doug Lytle wrote:
 Dave Fullerton wrote:
 Note num and not number I don't know if that was a change from 1.4
 to 1.6 or if Doug mistyped it.

 
 Not a mistype.  I've been using number all along, but looking at the 
 docs shows that I've been incorrect.  It must concatenate the number 
 down to num.  Looks like I've got a little modifying to do this evening:
 
 
 core show function CALLERID
 livonia*CLI
-= Info about function 'CALLERID' =-
 
 [Syntax]
 CALLERID(datatype[,optional-CID])
 
 [Synopsis]
 Gets or sets Caller*ID data on the channel.
 
 [Description]
 Gets or sets Caller*ID data on the channel.  The allowable datatypes
 are all, name, *num*, ANI, DNID, RDNIS.
 Uses channel callerid by default or optional callerid, if specified.
 
 Doug
 

The documentation is correct, but the way the check really works, is that it
reads the first 3 chars and matches it to num.

This means that num, number, and numnumnumIloveapplesauce would all
technically match.

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Danny Nicholas
But as Captain Hook would say, using number is bad form .  What does not
bite us now will eventually get us in a future update.

-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Jason Parker
Sent: Tuesday, November 10, 2009 1:09 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Setting outgoing callerid on when using a PRI

Doug Lytle wrote:
 Dave Fullerton wrote:
 Note num and not number I don't know if that was a change from 1.4
 to 1.6 or if Doug mistyped it.

 
 Not a mistype.  I've been using number all along, but looking at the 
 docs shows that I've been incorrect.  It must concatenate the number 
 down to num.  Looks like I've got a little modifying to do this evening:
 
 
 core show function CALLERID
 livonia*CLI
-= Info about function 'CALLERID' =-
 
 [Syntax]
 CALLERID(datatype[,optional-CID])
 
 [Synopsis]
 Gets or sets Caller*ID data on the channel.
 
 [Description]
 Gets or sets Caller*ID data on the channel.  The allowable datatypes
 are all, name, *num*, ANI, DNID, RDNIS.
 Uses channel callerid by default or optional callerid, if specified.
 
 Doug
 

The documentation is correct, but the way the check really works, is that it
reads the first 3 chars and matches it to num.

This means that num, number, and numnumnumIloveapplesauce would all
technically match.

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Dave Fullerton
Jason Parker wrote:
 Doug Lytle wrote:
 Dave Fullerton wrote:
 Note num and not number I don't know if that was a change from 1.4
 to 1.6 or if Doug mistyped it.

 Not a mistype.  I've been using number all along, but looking at the 
 docs shows that I've been incorrect.  It must concatenate the number 
 down to num.  Looks like I've got a little modifying to do this evening:


 core show function CALLERID
 livonia*CLI
-= Info about function 'CALLERID' =-

 [Syntax]
 CALLERID(datatype[,optional-CID])

 [Synopsis]
 Gets or sets Caller*ID data on the channel.

 [Description]
 Gets or sets Caller*ID data on the channel.  The allowable datatypes
 are all, name, *num*, ANI, DNID, RDNIS.
 Uses channel callerid by default or optional callerid, if specified.

 Doug

 
 The documentation is correct, but the way the check really works, is that it
 reads the first 3 chars and matches it to num.
 
 This means that num, number, and numnumnumIloveapplesauce would all
 technically match.

lol. Love it. I want to use that in my dialplan just to make my 
successor go WTF?

-Dave

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Doug Lytle
Dave Fullerton wrote:

 lol. Love it. I want to use that in my dialplan just to make my
 successor go WTF?



I almost lost a mouth full of coffee!!

*snicker*

Doug



-- 

Ben Franklin quote:

Those who would give up Essential Liberty to purchase a little Temporary 
Safety, deserve neither Liberty nor Safety.


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Setting outgoing callerid on when using a PRI

2009-11-10 Thread Danny Nicholas
I'm gonna put that CALLERID(numWTF) in my dialplan as well...

-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Doug Lytle
Sent: Tuesday, November 10, 2009 1:35 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Setting outgoing callerid on when using a PRI

Dave Fullerton wrote:

 lol. Love it. I want to use that in my dialplan just to make my
 successor go WTF?



I almost lost a mouth full of coffee!!

*snicker*

Doug



-- 

Ben Franklin quote:

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety.


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users