similar to: CAMA MF signaling for a 911 Trunk

Displaying 20 results from an estimated 600 matches similar to: "CAMA MF signaling for a 911 Trunk"

2003 Dec 14
1
Two Stage Dialing for MF CAMA trunk
Hi all, I am trying to setup a ZAP interface to do MF signaling for a handoff to a 911 tandem. The signaling I need to perform on the T1 is this: 9-1-1 Tandem: Wink CLEC end office: KP (Keypulse) NPA ST (Start) 9-1-1 Tandem: Wink CLEC end office: KP I (Info Digit) NXX XXXX ST As I'm not as familiar with the Zaptel configurabliity, I'm not really sure how to do this. Do I dial twice
2008 Jul 09
0
e911/CAMA/MF
Does anyone have any experience getting inbound ANI information from a CAMA/MF/E&M Wink trunk on Asterisk? Is this only do-able with a PRI interface? Any information would be helpful.
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
2012 Jun 28
0
[klibc:master] nfsmount: Fix wrong NFS umount path
Commit-ID: 029622dfbfe25203275a385a5bf33d44c2409b00 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=029622dfbfe25203275a385a5bf33d44c2409b00 Author: Benjamin Cama <benjamin.cama at telecom-bretagne.eu> AuthorDate: Fri, 22 Jun 2012 12:17:01 +0200 Committer: maximilian attems <max at stro.at> CommitDate: Thu, 28 Jun 2012 17:23:14 +0200 [klibc] nfsmount: Fix
2012 Jun 22
1
[PATCH] Fix wrong NFS umount path
Hi, When mounting a NFS share and an error occurs for some reason, the NFS share is not unmounted correctly: the local path is used instead of the remote path in the umount_v[23]() call. This patch fixes this. I found this while debugging some problems mounting the root file system on NFS in a test system; I saw this in the logs (/mnt/duplicated is the legitimate remote path): Jun 21
2005 Jul 01
1
no voice
Hi All We are unable to hear any voice where as in tcpdum it shows that RTP is flowing both ways ERROR CONDITION --------------- -- Executing Dial("SIP/2001-f6c4", "SIP/2000|20") in new stack -- Called 2000 -- SIP/2000-0ead is ringing -- SIP/2000-0ead answered SIP/2001-f6c4 -- Attempting native bridge of SIP/2001-f6c4 and SIP/2000-0ead Have searched web and
2010 Apr 25
2
[git pull] small fixes, sh4, getruage() README's
hello hpa, current patch queue for review, please pull: git pull git://git.debian.org/users/maks/klibc.git maks Aurelien Jarno (1): [klibc] sh4: syscalls fixes Benjamin Cama (1): [klibc] fstype: btrfs size endianness fix Thorsten Glaser (1): [klibc] add getrusage() maximilian attems (3): [klibc] resume: silence warning on resume try [klibc] bootp_packet.h minor
2010 Apr 03
1
[PATCH] btrfs support
Hi, As I use btrfs as root FS, I wanted fstype to be able to recognize it. The following patch add support for this FS. Regards, benjamin Signed-off-by: Benjamin Cama <benoar at free.fr> --- diff --git a/usr/kinit/fstype/btrfs_fs.h b/usr/kinit/fstype/btrfs_fs.h new file mode 100644 index 0000000..e1f933e --- /dev/null +++ b/usr/kinit/fstype/btrfs_fs.h @@ -0,0 +1,51 @@ +#ifndef
2003 Dec 11
0
Problem with R2 signaling
Hello, I am in Argentina configuring an E1 in R2 and have some inconveniences. When the call takes the salient line, I receive an error of signaling. In * I have loaded the following: - libr2 installed - The [ar] in zonedata.c and indications.conf is configured - zaptel.conf o: span=1,0,0,ccs,hdb3,crc4 span=2,0,0,cas,hdb3 #span1 bchan=1-15,17-31 dchan=16 #span2 cas=32-62:1001
2003 Nov 07
0
Re: Asterisk-Users digest, Vol 1 #1835 - 12 msgs
Thanks Brian, and thanks again for the included definitions <grin> - that helped too. Your comments are really helping clear many questions. I suppose our intensions are to become an IXC. So if my local carrier is sporting old technology, they'll provide TDM services. So if I understood you correctly, the "in-band signaling" is typically SS7, and the alternative is typically
2013 Sep 27
1
RV: cronbach
rm(list = ls()) #borra todo lo anterior en memoria setwd("G:/Public/Documents/R/EPICALC/") #como se llama la data desde su path sanda<-read.csv("sandavid2.csv",header=TRUE, sep=",", dec=".") use(sanda) attach (sanda) library (MASS) label.cronbach <- label.var(p01, "¿Consume mucho pan? ") ####¿Hay alguna manera de nombrarlos
2008 Jan 23
0
Lingvopedia as "Language solutions company"
Dear Sir/Madam, Greetings! We take the opportunity to introduce Lingvopedia as "Language solutions company" offering" End to End" Language consultancy. www.lingvopedia.com is an alliance promoted by Rahul Malik who has a vision to make a significant positive difference in the overall needs of our guests and to become a market leader in linguistic services. The purpose of
2004 Apr 08
0
(no subject)
Sub: INTRODUCTION FOR SUPPLY OF SPECIAL CABLES We have pleasure in introducing ourselves as manufacturer's of specialised cables for over two decades catering to the needs of the Fertilizer, Chemical, Petrochemical, Oil & Gas, Steel, Power, Cement, Ceramic, Glass, Paper, Sugar and other industries. The following are some of the cables made by us: ANY CABLE, ANY TIME, ANY QUANTITY
2010 Jul 07
0
[git pull v2] x86_32, sh4, getrusage()
hello hpa, here my birthday submission :) please pull: git pull git://git.debian.org/users/maks/klibc.git maks Sam fixed a longstanding x86_32 build bug, thus it seems a good time to flush the queue of the piled up patches, the shortlog tells it: Aurelien Jarno (1): [klibc] sh4: syscalls fixes Benjamin Cama (1): [klibc] fstype: btrfs size endianness fix Mike Waychison (2):
2006 Apr 04
1
Ideal Setup for T1/PRI and TE110P - second try
Hi all, I'm sure something similar has been discussed, but one can only wade through the archives for so long. I'm setting up a T1 and my telco has a bunch of questions it wants me to answer. I know much of the TE110p is configurable to do any of this, but I wanted to know if there is an optimal or preferred setup. Any help would be appreciated. Here is the quiz my telco is giving me:
2004 Jul 24
3
Help with T1 PRI Configuration
I'm ordering a PRI T1 for use with Asterisk and a Digium Wildcard TE405P. The provider is asking me a number of questions about how I want to configure the line. Here goes: 1. Dial Tone - No, Yes - Precise, Yes - SCC 2. Framing - SF, ESF 3. Line Coding - AMI, B8ZS 4. Signaling Type - Ground Start, E&M, Loop Start w/Ring, Loop Start w/o Ring 5. Pulse Mode - DTMF, MF 6. Outpulse Start -
2014 Jan 31
0
e911 Signalling
Hi, We've got a dedicated T1 with two trunks running into our ILECs selective router for 911. Split out of the T1 into two MF CAMA trunks on ILEC side. I'm trying to use asterisks e911 signaling, but I'm having trouble with the dial command. (== Everyone is busy/congested at this time (1:1/0/0)) I'm missing something and I'm thinking it has to do with the hookstate
2006 Apr 04
1
Ideal setup for PRI/T1 and TE110P
Hi all, I'm sure something similar has been discussed, but one can only wade through the archives for so long. I'm setting up a T1 and my telco has a bunch of questions it wants me to answer. I know much of the TE110p is configurable to do any of this, but I wanted to know if there is an optimal or preferred setup. Any help would be appreciated. Here is the quiz my telco is giving me:
2006 Apr 03
2
Blocked channels, according to our telco... leading to CONGESTION status
Greetings, Our telco called last week, saying that a lot of channels on our PRIs are blocked. And with blocked they have the following description in the Siemens exchanges: BBAC BLOCKED BACKWARD This status is set when the partner exchange has a blocking set and the signaling of the trunk (non-CCS7) is able to report this blocking in the backward direction. This status can