I switched PRI vendors recently, and one of my questions was "do you provide caller ID name in addition to number?" AT&T Local did not, But XO communications said they did. Before I call to complain, is there an setting to turn this on in asterisk? I want to make sure that I have my side covered before I call XO. My current zaptel.conf is: context=from-pstn switchtype=national pridialplan=unknown prilocaldialplan=unknown priindication = outofband signalling=pri_cpe usecallerid=yes hidecallerid=no usecallingpres=yes echocancel=yes echocancelwhenbridged=no group=0 callgroup=1 pickupgroup=1 accountcode=I musiconhold=default channel => 1-23 -- -- Steven http://www.glimasoutheast.org
There is nothing you really need 'to do' if your PRI is working already, If you are able to receive and make calls your D-Channel is functioning properly. In the case of CallerID, some telcos provide this extra function via the FACILITY messages instead of the SETUP messages, If that is the case, you will get no Name but you will get a number. IT simply means that Asterisk answered the call with the SETUP message but was unable to read in the CALLERID Name to pass on to your devices because it comes later on in the call via the FACILITY. Add a Wait(2) before you answer the call for your PRI, see if that helps.> -----Original Message----- > From: asterisk-users-bounces@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Steven > Sent: Monday, April 10, 2006 8:57 AM > To: asterisk-users@lists.digium.com > Subject: [Asterisk-Users] callerid name inboune from PRI > > I switched PRI vendors recently, and one of my questions was > "do you provide caller ID name in addition to number?" > AT&T Local did not, But XO communications said they did. > > Before I call to complain, is there an setting to turn this > on in asterisk? > I want to make sure that I have my side covered before I call XO. > > My current zaptel.conf is: > > context=from-pstn > switchtype=national > pridialplan=unknown > prilocaldialplan=unknown > priindication = outofband > signalling=pri_cpe > usecallerid=yes > hidecallerid=no > usecallingpres=yes > echocancel=yes > echocancelwhenbridged=no > group=0 > callgroup=1 > pickupgroup=1 > accountcode=I > musiconhold=default > channel => 1-23 > > > > > -- > -- > Steven > > http://www.glimasoutheast.org > > > > > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
Don't set immediate=yes, = BAD.
ON your 'did-exten' prepend a step that adds the wait.
Like so:
Wait(2)
NoOp(${CALLERID(num)})
NoOp(${CALLERIS(name)})
Dial(.....)
>>-----Original Message-----
>>From: asterisk-users-bounces@lists.digium.com
>>[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Steven
>>Sent: Monday, April 10, 2006 1:36 PM
>>To: asterisk-users@lists.digium.com
>>Subject: [Asterisk-Users] Re: callerid name inboune from PRI
>>
>>Thanks for the info.
>>
>>I went to add the Wait(2), but am unsure where to do it.
>>My context is "from-pstn".
>>
>>My [from-pstn] is:
>>[from-pstn]
>>exten => s,1,NoOp(${TIMESTAMP} PRI call in) ; I tried
>>adding this to see if "s" is used, but lothing was logged.
>>include => from-pstn-custom ; create this
>>context in extensions_custom.conf to include customizations
>>include => ext-did
>>exten => fax,1,Goto(ext-fax,in_fax,1)
>>
>>My "from-pstn-custom" is non-existent and my
"ext-did" is
>>just an include for "ext-local", which is my inside
extensions.
>>
>>If I understand you correctly, I need the wait before I pick
>>up the line.
>>If I change the span to immediate=yes, I can use the "s"
>>extension, but It would also answer the line early.
>>
>>I am drawing a blank where to put the wait.
>>
>>Please advise.
>>
>>
>>
>>
>>
>>
>>--
>>--
>>Steven
>>
>>http://www.glimasoutheast.org
>>
>>
>>
>>"Alexander Lopez" <Alex.Lopez@OpSys.com> wrote in
message
>>news:E918F2FD95450648B7F8C957D92D5271422822@exmail.corp.opsys.com...
>>There is nothing you really need 'to do' if your PRI is
>>working already, If you are able to receive and make calls
>>your D-Channel is functioning properly. In the case of
>>CallerID, some telcos provide this extra function via the
>>FACILITY messages instead of the SETUP messages, If that is
>>the case, you will get no Name but you will get a number. IT
>>simply means that Asterisk answered the call with the SETUP
>>message but was unable to read in the CALLERID Name to pass
>>on to your devices because it comes later on in the call via
>>the FACILITY.
>>
>>Add a Wait(2) before you answer the call for your PRI, see if
>>that helps.
>>
>>
>>
>>> -----Original Message-----
>>> From: asterisk-users-bounces@lists.digium.com
>>> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of
Steven
>>> Sent: Monday, April 10, 2006 8:57 AM
>>> To: asterisk-users@lists.digium.com
>>> Subject: [Asterisk-Users] callerid name inboune from PRI
>>>
>>> I switched PRI vendors recently, and one of my questions
>>was "do you
>>> provide caller ID name in addition to number?"
>>> AT&T Local did not, But XO communications said they did.
>>>
>>> Before I call to complain, is there an setting to turn this on in
>>> asterisk?
>>> I want to make sure that I have my side covered before I call XO.
>>>
>>> My current zaptel.conf is:
>>>
>>> context=from-pstn
>>> switchtype=national
>>> pridialplan=unknown
>>> prilocaldialplan=unknown
>>> priindication = outofband
>>> signalling=pri_cpe
>>> usecallerid=yes
>>> hidecallerid=no
>>> usecallingpres=yes
>>> echocancel=yes
>>> echocancelwhenbridged=no
>>> group=0
>>> callgroup=1
>>> pickupgroup=1
>>> accountcode=I
>>> musiconhold=default
>>> channel => 1-23
>>>
>>>
>>>
>>>
>>> --
>>> --
>>> Steven
>>>
>>> http://www.glimasoutheast.org
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> --Bandwidth and Colocation provided by Easynews.com --
>>>
>>> Asterisk-Users mailing list
>>> To UNSUBSCRIBE or update options visit:
>>> http://lists.digium.com/mailman/listinfo/asterisk-users
>>>
>>_______________________________________________
>>--Bandwidth and Colocation provided by Easynews.com --
>>
>>Asterisk-Users mailing list
>>To UNSUBSCRIBE or update options visit:
>> http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>>
>>
>>_______________________________________________
>>--Bandwidth and Colocation provided by Easynews.com --
>>
>>Asterisk-Users mailing list
>>To UNSUBSCRIBE or update options visit:
>> http://lists.digium.com/mailman/listinfo/asterisk-users
>>
Steven wrote:>I switched PRI vendors recently, and one of my questions was "do you provide caller ID name in addition to number?" >AT&T Local did not, But XO communications said they did. > >You heard wrong. We have multiple PRIs from XO and they DO NOT send caller name. We have discussed the issue with them on several ocassions. The sales people will say whatever they want, but the tech people who actually work in the switches know that caller name is not supported.>Before I call to complain, is there an setting to turn this on in asterisk? >I want to make sure that I have my side covered before I call XO. > >My current zaptel.conf is: > >context=from-pstn >switchtype=national >pridialplan=unknown >prilocaldialplan=unknown >priindication = outofband >signalling=pri_cpe >usecallerid=yes >hidecallerid=no >usecallingpres=yes >echocancel=yes >echocancelwhenbridged=no >group=0 >callgroup=1 >pickupgroup=1 >accountcode=I >musiconhold=default >channel => 1-23 > > > > > >-- Andres Technical Support http://www.telesip.net
On Mon, 2006-04-10 at 22:42 -0400, Andres wrote:> Steven wrote: > You heard wrong. We have multiple PRIs from XO and they DO NOT send > caller name. We have discussed the issue with them on several > ocassions. The sales people will say whatever they want, but the tech > people who actually work in the switches know that caller name is not > supported. >I would say it depends on the market and location as well, since XO has several flavors of switches and provisioning systems and has quite the disparate network. The ALGX infrastructure they purchased is very much still in place, and did provide CNAME on PRIs for extra cost. -Greg