CS1K to Asterisk with PRI/ISDN Card

[minicompbx]

Hello Guys,

Recently, I installed Asterisk on our network and I am trying to connect with CS1K.
I put PRI/ISDN Pci card on Asterisk server and connect it to CS1K server.

On the asterisk side, I think everything seem to be ok. I detect the card and configure it as needed
The card is : Wildcard TE122 Card

Mostly, I need help for CS1K. As I want to know how to add TMDI/DCH card and setup so the asterisk can communicate with CS1K
I connect the card on cabinet ... but I do not know what to next ... how to activate and setup
I put on the cabinet 0 0 card 5

I read the guide

http://www.ghtrout.com/

Asterisk to CS1K... I understand very well Asterisk part but not all step for CS1K
Another link with similar request :

http://lists.digium.com/pipermail/asterisk-users/2009-July/235294.html

Thank you


Learning is not enough, you have to apply it...

 

[minicompbx]

Forgot to mention I am using CS1K 7.0

Learning is not enough, you have to apply it...

 

[minicompbx]

I was hoping for some guide or help but it seem that I am answering for myself..

I did some more research and I followed the guide provided on GHTROUT website.

But I am stuck at the step of creating B-Channel (BCH)

I do not unserstand very well this step...

What is the TN that I have to provide ...do I need to create a new one. If yes, what is the configuration

Hoping this time someone will answer

Learning is not enough, you have to apply it...

 

[minicompbx]

Hello again,

I think I am answering for myself.. but anyway every advice are welcome

I did manage to create B-channel in ld 14.
For info : for the TN : I had to write dchannel# 1.
And the rest of the TN will be created automatically


Now, I am able to call CS1000 via asterisk but unable to call an extension of asterisk from CS1000
One of the thread I found :

http://www.tek-tips.com/viewthread.cfm?qid=1581576

Still doing more research but hope somebody will give some advice

Thanks

Learning is not enough, you have to apply it...

 

[jebloome]

On the CS1000, you need to basically do a route call. in other words, call the ACOD of the route and then send the 4 digits to an extension on the Asterisk. you have to tell the PBX where you want the call to go. i created a CDP in LD 87 to activate a DSC to route the call to our asterisk server. that should get you going. test it first by dialing the ACOD of the Route to the Asterisk server then send what ever you want. you should see the call hit the server.

 

[minicompbx]

Thank you for your kind reply... I did try to dial ACCOD directly and it was giving a busy sign.

So what I did that I compare another RDB which have ACOD working configuration with the one I created for the Asterisk.

Again doing some research I just found out the mistake I did is that in my rdb configuration I set the tgar to 1 and my set was also using targ 1. Therefore, it was always giving me the busy sign.(access denied)

This link help me a lot :

http://pbxbook.com/meridian/mer_tgar.html

I spent almost 20 min trying to remove the targ.... I tried 1 x or x 1 but what you have to do is 1x to remove the targ 1 in rdb. We never know ... hope somebody else might need it...

Thank's again for all readers and @jebloome for your reply.

Learning is not enough, you have to apply it...

 

[minicompbx]

Hello guys,

I think I am doing really a good progress .. thank's to a lot of old thread and google. But, I am still missing one thing.

The caller ID (DN and Name) are not sent to Asterisk. Instead, it send public number (123 456-7890). It seem that CS1K think that the card configured for asterisk is an external Link and it send public number.

My question, what I have to change so the CS1K can send DN and Name to Astersik

For the info, Astersik is able to send extension and name and it show's very well on CS1K

Learning is not enough, you have to apply it...

 

[yyrkroon]

My question, what I have to change so the CS1K can send DN and Name to Astersik


Not sure what you're using for the DCH protocol, but if it's NI2 - then add NDS to the RCAP in the DCH programming, this is for name delivery on NI2 protocol.

 

[minicompbx]

No I am not using NI2. Below the config of my ADAN.
Actually, I tried to put NDS to RCAP but get the error SCH0843 (NDS valid only for NI-2 interface)

ADAN     DCH **
  CTYP TMDI 
  MG_CARD  ***** 
  PORT 1 
  DES  ASTERISK
  USR  PRI 
  DCHL ** 
  OTBF 32 
  PARM RS232  DTE 
  DRAT 64KC
  CLOK EXT 
  IFC  [b]ESS5[/b]
  SIDE USR 
  CNEG 1 
  RLS  ID  1 
  RCAP ND2 
  MBGA NO
  OVLR NO
  OVLS NO
  T200 3 
  T203 10 
  N200 3 
  N201 260 
  K    7

Learning is not enough, you have to apply it...

 

[yyrkroon]

With ESS5 protocol, you'll have to play with the different options - ND1, ND2 or ND3 - you can try NDI or NDO but I thinks those are for QSIG interface only.

Remember, you'll have to perform a force download to the TMDI each time you change the NDx option.

After each change, you might want to turn on DCH messaging and set the facility message level to 2 - it could be the M1 is sending name, but the end is rejecting it and you're not going to see it unless you turn on DCH messaging.

 

[minicompbx]

How to know or what are the option available for ESS5 RCAP protocol.
For me, I can only enter ND2 but it does not fix the clid issue
All other options gave me error message

Learning is not enough, you have to apply it...

 

[hawks]

The only time I've been able to get name and number over a privite network is with either QSIG or SL1 set as my protocol. You might be able to so something with the clid table but I'm not sure.

 

[yyrkroon]

Go to LD96 and type the following

ENL MSGO X - where x is your DCH in question
ENL MSGI X

SET MSGO X MON 2

stay in LD 96 make a test call and post the result, I'll bet that you're sending the info, the other end is rejecting it.

To disable:

DIS MSGO X
DIS MSGI X

SET MSGO X MON 0 or leave it at MON 2

 

[minicompbx]

Hello @yyrkroon,

Just for the update, I already did that and no system is not sending the correct info. I thinking of rebuilding the DCH with SL1 unless you have another solution
I am calling 1122 from the CS1K

The output is :

DCH ** OMSG SETUP    REF 00000012 CH ** 18 TOD   9:37:53 
CALLING #:1234567890     NUM PLAN: E163/NATIONAL (UNKNOWN) 
CALLED  #:1122           NUM PLAN: E163/NATIONAL (UNKNOWN) 

    DCH ** IMSG CALLPROC REF 00000012 CH ** 18 TOD   9:37:53 

    DCH ** IMSG ALERT    REF 00000012 CH ** 18 TOD   9:37:53 
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

    DCH ** OMSG DISC     REF 00000012 CH ** 18 TOD   9:38:19 
CAUSE :NORMAL CALL CLEARING

Learning is not enough, you have to apply it...

 

[yyrkroon]

You didn't set the monitor level to 2, it's still showing level 0 info. You'll know it's level 2, because everything is in HEX.

You're probably better off changing it to a different protocol, easier and faster in the long run...good luck

 

[minicompbx]

I just recreate the DCH with ESS5 as I did in the beginning and same way the asterisk. It is working like before

For the DN I will have to play with CLID (I might need a hand for CLID)

As we have some set with Nortel and some with Asterisk.

For example how do I create a clid that will send DN and Name to Nortel set and only dn to Asterisk ... on ld 15

Any guide will be appreciate.

Thank's

Learning is not enough, you have to apply it...