Displaying 9 results from an estimated 9 matches for "singnaling".
Did you mean:
signaling
2006 Nov 06
0
Re: Definity ISDN PRI
...general application. This also makes routing on the Asterisk a lot simpler.
Easy to make the changes.... will advise if desired.
Mark
> isdn-pri/line-side, protocol b, and a I think were using a TN464
> card on the definity. I'll have to check on the card. We are
> using pri_net singnaling and national is our switchtype in
> asterisk. I'll try the changes and report back. Thank you so much!
>
> -CP
>
> ________________________________________
> From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-
> users-bounces@lists.digium.com] On Behalf Of ma...
2006 Jun 17
0
T1 + E&M
Maybe of you guys know the answer to this:
We have T1's that come from both MCI and Global Crossing as channelized (24
Ports per T) with inband (DTMF) delivery
of ANI and DNIS (format = *DNIS*ANI*). My old equipment was set for D4,
AMI, SF and Wink Start and so is Asterisk. I've moved these T's to Asterisk
TE410P and inbound calls are arriving to external voice mail system
2006 Jun 17
0
E&M + Dial tone
Maybe of you guys know the answer to this:
We have T1's that come from both MCI and Global Crossing as channelized (24
Ports per T) with inband (DTMF) delivery
of ANI and DNIS (format = *DNIS*ANI*). My old equipment was set for D4,
AMI, SF and Wink Start and so is Asterisk. I've moved these T's to Asterisk
TE410P and inbound calls are arriving to external voice mail system
correctly
2006 Nov 05
1
Definity Asterisk Caller ID Issue
You should run the 4ESS protocol ("a" on the Definity command "change DS1 board#) as the Definity may not send Display Name for the NI-2 protocol (settings "b" or "d")
Remember to make the Asterisk zapata settings consistent with the Definity.
On the Definity trunk group form Page 1, change "Codeset to send Display" to "0 (zero)", also make
2019 Jan 25
0
[klibc:update-dash] trap: Globally rename pendingsigs to pending_sig
Commit-ID: dbb7e738b59fe626fd25c4df9f348fecc434ce09
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=dbb7e738b59fe626fd25c4df9f348fecc434ce09
Author: Denys Vlasenko <dvlasenk at redhat.com>
AuthorDate: Wed, 26 Oct 2016 19:28:29 +0200
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Fri, 25 Jan 2019 02:57:21 +0000
[klibc] trap: Globally rename
2020 Mar 28
0
[klibc:update-dash] dash: trap: Globally rename pendingsigs to pending_sig
Commit-ID: e0829af46211f7919afe8f49dd3145c0cbb45d87
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=e0829af46211f7919afe8f49dd3145c0cbb45d87
Author: Denys Vlasenko <dvlasenk at redhat.com>
AuthorDate: Wed, 26 Oct 2016 19:28:29 +0200
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 28 Mar 2020 21:42:54 +0000
[klibc] dash: trap: Globally
2019 Dec 14
3
USB dahdi fxo ?
On 12/14/19 11:29 AM, Greg Troxel wrote:
> sean darcy <seandarcy2 at gmail.com> writes:
>
>>> There is also the ObiHai OBi202 with an OBiLine, which provides an FXO
>>> port remoted over SIP. (I am not sure if this is discontinued.)
>>
>> "FXO port remoted over SIP"?
>>
>> I have an analog phone system. I can use the obi202 to
2005 May 12
5
chan_capi, chan_misdn and chan_modem
Could someone please comment on the current state of chan_capi,
chan_misdn and chan_modem channel drivers in terms of functionality and
stability. Specifically, which channel driver would be best for a
passive PCI HFC or W6692 ISDN card. The chan_misdn wiki claims that
chan_capi distinguishes between junghanns and non-junghans cards, and
that chan_misdn is better suited for general misdn
2004 Jan 12
1
E100P - connected to Cisco
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi,<br>
<br>
have any one sucessfully connected E100P to Cisco? I am