Hi,
I have a B410P card with bri_cpe signalling and two Openvox analog card
(A1200p, A800P) with fxo_ks signalling. From the ISDN we have
Point-Point 10 connection with a 10 public phone number range. If I
receive a public call, the asterisk recevies the last two digit from
this range, so it
Hi,
I'm using a ISDN-30 E1 line from KPN Belgium.
The challenge is to get a correct CallerID on outgoing lines.
When I put this in my dialplan:
exten = _0.,1,Set(TEMPVAR=${CALLERID(num):1})
exten = _0.,2,Set(CALLERID(num)=144622${TEMPVAR})
exten = _0.,3,NoOp(${CALLERID(num)})
exten =
Bart Coninckx wrote:
Hi,
I'm using a ISDN-30 E1 line from KPN Belgium.
The challenge is to get a correct CallerID on outgoing lines.
When I put this in my dialplan:
exten = _0.,1,Set(TEMPVAR=${CALLERID(num):1})
exten = _0.,2,Set(CALLERID(num)=144622${TEMPVAR})
exten =
Hi List,
i've set up an Asterisk 1.6.0.3 Server equipped with an Xorcom Astribank BRI
XR0013 (2 Port BRI) and Dahdi 2.1.0. In- and outgoing calls are no problem. But
I can't get Asterisk/DAHDI to use the second Number of the BRI. All calls set
the primary number as callerid. It wouldn't be a
I am not sure of the best way to do this, so I thought I would query the list.
I have about 100 internal extensions ranging from 2000 - 2100. Each
internal extension has a external DID number. For example: 2001 =
5552871620. As you can see the internal externsion and DID don't
match in any
On Thu, 19 Apr 2007, Forrest Beck said something to this effect:
I thought of maybe adding a key for each extension to the astdb and
have a Macro query the astdb. Any other ideas?
That would work, and is certainly the easiest, since you can bulk-load
the DID - extension maps via external
On 4/19/07, Forrest Beck [EMAIL PROTECTED] wrote:
I thought of maybe adding a key for each extension to the astdb and
have a Macro query the astdb. Any other ideas?
That's how we do it. We created a MySQL DB that maps DIDs to extensions, and
a php script to write our configuration files
Thanks. I will just use the asterisk database.
This brought up a new question though.
This is what I am using to dial out. If a key for the phone exist in
the db it will assign it the did specified. If not, just assign the
main incoming operator number.
I have a new family in the astdb
Hello
I have a problem with callerid in the manager interface.
I think that Asterisk has a strange way to handle callerid, until I
found out to set the o-switch in the DIAL statement, it did not work
the way I wanted, it still doesnt, but now it works ok in one
direction.
My extension is 311,
For outgoing calls made on our PRI circuit we are setting the Caller ID
using the format
Exten = _9XXX,1,SetCallerID(1601XXX)
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
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 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
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 = _9XXX,1,SetCallerID(1601XXX)
The monitor shows that the CallerID is being set to the specified
number, but yet when
as problems!
Rgds
Tim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of McInnis, JP
Sent: 29 June 2004 15:13
To: [EMAIL PROTECTED]
Subject: [Asterisk-Users] Outgoing CallerID on PRI problems
For outgoing calls made on our PRI circuit we are setting the Caller ID
Calling Number (len=12) [ Ext: 0 TON: International Number
(1) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)
Presentation: Presentation
permitted, user number passed network screening (1) '4330' ]
It might be that the number plan is international
JanM wrote:
Hello,
Does anyone know how to set the outgoing CallerID properly
when using Snom200/SIP/CAPI/BRI?
--SNIP--
My mobile is only showing some other number that my isdn
line is having.
---JanM---
Telecom restrictions?
I can set only caller IDs within the set of
JanM wrote:
Hello,
Does anyone know how to set the outgoing CallerID properly
when using Snom200/SIP/CAPI/BRI?
--SNIP--
My mobile is only showing some other number that my isdn
line is having.
---JanM---
Telecom restrictions?
I can set only caller IDs within
Calling Number (len=12) [ Ext: 0 TON: International Number (1) NPI: ISDN/Telephony
Numbering Plan (E.164/E.163) (1)
Presentation: Presentation permitted, user number passed
network screening (1) '4330' ]
It might be that the number plan is international
follows to ANI digits. Technically,
CallerID is only 1 byte that allow to hide o shows your ANI. Thats all...
Regards,
Gus
- Original Message -
From: Mickey Binder [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 16, 2003 4:09 PM
Subject: RE: [Asterisk-Users] Outgoing
Hello,
Does anyone know how to set the outgoing CallerID properly when using
Snom200/SIP/CAPI/BRI?
Following doesn´t work:
exten = _0.,1,SetCallerID,526910
exten = _0.,2,Dial,CAPI/526980:${EXTEN:1}
Asterisk writes:
*CLI -- Executing SetCallerID(SIP/226-ada0, 526910) in new stack
--
JanM wrote:
Hello,
Does anyone know how to set the outgoing CallerID properly when using
Snom200/SIP/CAPI/BRI?
Following doesn´t work:
exten = _0.,1,SetCallerID,526910
exten = _0.,2,Dial,CAPI/526980:${EXTEN:1}
Asterisk writes:
*CLI -- Executing SetCallerID(SIP/226-ada0, 526910)
Is there a way for me to set my outgoing callerid string so that all
callers outside of my pbx see our callerid string as company name main
company number but callers inside our telephone network see extension
holders name extension number? In looking at the references it looks like
I can do
You can set this in zapata.conf.
Basically, you just define the callerid before you define the channel.
Outgoing channels will have the callerid of the company, and internal
channels will have the callerid of the extension.
In zapata.conf
Example:
;I don't think you have to change anything in the
You can use the SetCallerID application to do this, as well.
Whenever a call is destined for the outside world, just
SetCallerID(13334445)
Am I missing something more complex here?
Of course, you'll need to have a PRI to do this, and 1333444
needs to be a permitted number for your
24 matches
Mail list logo
