Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Asterisk to M1 via robbed-bit T1 1

Status
Not open for further replies.

mwood5885

Vendor
Sep 9, 2005
12
US
I have successfully connected my Asterisk server to my Option 61c via robbed-bit T1, and set up the co-ordinated dialing plan. Station to station calls from Asterisk to Meridian work fine. BUT, I can't dial out to local or long distance from the Asterisk using the Meridian. Any calls sent to the Meridian that are not station calls are routed to the attendant. Also I cannot transfer an external call FROM the Meridian to the Asterisk. Somewhere it is restricted, can someone point me to a likely solution?

Thanks
 
Thanks for the reply, I made the changes and still no joy. Where else could I look?
 
ARE THE NCOS OF THE INCOMING TRUNKS HIGH ENOUGH TO DIAL OUT

OLD ROLMEN WORKING ON NORTELS
 
WHAT NCOS ARE YOUR LOCAL PHONES TO CALL OUT

OLD ROLMEN WORKING ON NORTELS
 
CHANGE THE NCOS OF THE TRUNKS TO A 7

OLD ROLMEN WORKING ON NORTELS
 
Sorry if this appears twice or was directed to another spot - PC ascting very normal today.
------------------
When the Asterisk tries to call to another company: they dial 9 the call connects over the T1 to the Meridian and the Meridian should pass it over a trunk and then the digits are output towards the telco and the call is completed. I will assume that is what you want to happen - that is the norm.


On an interoffice call, where Asterisk users call Meridian Users or Meridian users call Asterisk users - all is fine. I will assume that is the case.


So, when Asterisk user wants to dial to an "external/outside the company" number:


---Asterisk user dials 9 which selects a free TIE line from the T1


---Meridian 1 returns internal/normal station dial tone to Asterisk


---The Asterisk user dials "12125551212"


---Meridian hears the "12125551212" -


---That raises the first question - does the Asterisk know that after a user dials 9, it needs to seize a TIE line then send 9 to the Meridian too. On lots of systems, when a remote user dials 9, we just inserted another 9 - Other wise, they would have to dial 99+ tele number


---The second question is "If the Meridian is processing "dial 9" calls that come from TIE trunks, then the TIE trunk need to have NCOS like any phone would or the call may be restricted

~
 
Okay,

So I went back into LD 14 and changed the NCOS of each trunk to match what I have in the sets (ld 11) NCOS. In this case it is “7”. Calls intended for outside access are still intercepting to the attendant. I checked with the Asterisk system to see what digits are being passed to the Meridian over the T1 and it shows that the “9” is being prepended to the number. Is there a facility on the Meridian to output what it is seeing from the Asterisk? I tried looking at the CDR but nothing is printing for the intersystem traffic. Maybe I need to check things in the route (ld 16) for CDR output.

 
If in LD87 NCTL, the NCOS 7 = FRL 7 , then you have eliminated NCOS.

You will want to use the LD80 trace commands and the "DEV" suffix.

So, if Loop 4 chanel 1 is the call getting the attendant,

LD 80

.TRAD 4 1 DEV

The DEV adds on various restriction ifno

~
 
here is the trace from ld 80.
ACTIVE TN 012 01
ORIG 012 01 DID RMBR 8 1
TERM DN 6000
TDTN 0 SLOT 30 PTY SLOT 30
DIAL DN 6000
MAIN_PM RING AUX_PM
TALKSLOT ORIG 30 TERM 30
EES_DATA:
NONE
QUEU RING
CALL ID 0 947

COS_ORIG UNR COS_TER UNR
TGAR_ORIG 0 TGAR_TER 0
NCOS_ORIG 7 NCOS_TER NONE
EXP_ROUTE NO

I went to ld 87 and added NCOS =7 and FRL = 7
the DN 6000 is the VM port, the system is currently in nights. So the intercept to the operator is still going on
 
TYPE RDB
CUST 00
ROUT 8
DES ASTERISK_VOIP
TKTP DID
SAT NO
RCLS EXT
DTRK YES
DGTP DTI
DSEL VOD
PTYP DCO
AUTO NO
DNIS NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 6408
CPP NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
TFD 0
SST 5 0
NEDC ETH
FEDC ETH
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR YES
INC YES
LAST YES
QREC YES
OAL YES
AIA NO
OAN NO
OPD NO
NATL YES
MUS YES
MRT 1
EQAR NO
FRL 0 0


PAGE 002

FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
OHTD NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO


TN 012 01
TYPE DID
CUST 0
NCOS 7
RTMB 8 1
NITE
SIGL EM4
STRI/STRO WNK WNK
SUPN YES
AST NO
IAPG 0
CLS UNR DTN ECD WTA LPR APN THFD HKD
P10 VNL
TKID
DATE 25 MAY 2006
 
LD 14 OUT the first two channels the asterisk would hit, then create a new Trunk Route as a TIE (only add in the Meridian - no changesw in Asterisk)

Rebuild the two trunk TNs into that new TIE route and test. if it fails, at least you can get back to where you were with just two TNs to change.



~
 
Changed the 2 trunks to type TIE and built new Route. Calls from the Asterisk ring to a fast busy, both internal and external. Calls from the M1 to the Asterisk ring fine, however still could not transfer an external call from the M1 to the Asterisk.
 
OK, keep the route built - - just put the trunks back as you need to break away from the testing.

Next I would change EM4 on the LD14 Trunk to EAM (The SIGL prompt) - dunno why, just gut intuition

You could try LDR too - but at least these are quick TN changes.

~
 
Changed trunk to SIGL EAM, calls still ring to busy. Also worth mentioning internal calls can be transferred to the Asterisk. But anything to do with an external trunk will not work
 
I just rechecked all RDB's and the NEDC and FEDC are both set to ETH.......
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top