Cisco ATA 188 with a CS1000 (Option 11C) 2

[ELBeast]

Hi,
I was wondering if anyone knew how to get the Cisco ATA 188 to work w/ the Succession CS1000 VOIP. I want to hook up a fax machine at an office across town. We already have I2004s working over there I just don't know I what settings I would need to configure (ATA to CS1000 and vice versa).
This should work being that both devices support SIP and H.323. Or if anyone knows how to setup/program a non-Nortel H.323 device in the CS1000.
Any direction or assistance would be greatly appreciated.

Thanks,
STEVE

 

[3tdp33ler]

If you have H.323 trunks and NRS you can try to register ATA as H323 endpoint.

 

[ELBeast]

How do I create H.323 virtual trunks? I can create a gateway endpoint in the NRS but what do from there?

 

[dlesap]

Create Virtual DCH, virtual rout, members with Element manager or with command line. Then a classical DSC pointing to RLI with the Virtual rout number.

NRS have to route calls in both ways also: Routing entry tab

 

[ELBeast]

How would I do that? I'm a relative newbie to the Nortel line,
Thanks!

 

[I2007]

That is a good question. The setup for this in the pabx is not very complex, but at the same time it is. I recommend you to take some training courses with nortel before you do too much by yourselves, if you are a newbie as you said? I would recommend you to go to a Nortel vendor and ask them to install it, and at the same time learn from what they are doing.

sat2phant

 

[ELBeast]

OK, so I figured it out (somewhat).
I created a entry in the DSC with the digits 7059
I then pointed it to our H.323 trunks route 20
I created an entry in the NRS with the H.323 ID and I added this ID to the ATA188. I can get the device to register with NRS and I can call my ext at my desk. I can call the analog phone off the device via my desk phone or my cell phone. So I can call the device from outside our H.323 network. I just can't make any calls from the ATA to the outside world. I just get busy signals. Here is a print out of some debugging info from the ATA:
060320|11:28:32 [0]DTMF 8 , insum:980153
060320|11:28:32 1:00;0,0,0,0,
060320|11:28:33 [0]DTMF 5 , insum:1025792
060320|11:28:33 [0]DTMF 3 , insum:1014943
060320|11:28:34 [0]DTMF 0 , insum:1004663
060320|11:28:34 [0]DTMF 0 , insum:982949
060320|11:28:38 Calling 93385300
060320|11:28:38 SCC->(0 0) <cmd 16>
060320|11:28:38 CLIP
060320|11:28:38 SCC->(0 0) <cmd 2>
060320|11:28:38 <0 0> dial<93385300>
060320|11:28:38 GK<-0: ARQ: 0
060320|11:28:38 GK: AdmissionReject reject reason: 2
060320|11:28:38 CallRasCallBack: 0 33e1989 33e2528 33e3fe3
060320|11:28:38 SCC:ev=7[0:0] 3 0
060320|11:28:38 [0]StartTone 2
060320|11:28:41 S1
060320|11:28:41 GK<-0: KPA-RRQ:30 sec
060320|11:28:41 GK->0: RCF:TTL 30
060320|11:28:43 SCC->(0 0) <cmd 20>
060320|11:28:43 SCC->(0 1) <cmd 20>
060320|11:28:43 [0]StopTone
060320|11:28:43 SCC->(0 0) <cmd 1>
060320|11:28:43 CCBS expired
060320|11:28:43 [0]MPT mode 0
060320|11:28:43 SCC->(0 0) <cmd 0>

I Googled "GK: AdmissionReject reject reason: 2" and the closest thing I could find a reference for was a invalid password. So I disabled the endpoint authentication, and I still get the same error. Any ideas??

 

[3tdp33ler]

Check and try to change NCOS and TGAR on your H323 trunks.
Very likely they are not enough to override access restrictions assigned for outgoing calls.

 

[dlesap]

I never try to registered Cisco ATA but Audiocodes ones, see Thread 798-1031624.

These system are the same.
I first get the same result as you. The solution is in the ATA boxe. Here is a print of the ATA config i had. Hope you can find something same as Cisco ATA

H.323 Protocol Definition
General
* Connection Mode Normal
* Enable Annex D/T.38 FAX relay Yes
* Enable DTMF over H.245 No
H.323-ID : MP124_1
* Source Number Encoding Type E.164
* Destination Number Encoding Type E.164
* Q.931 Multiplexing No
Gatekeeper
Working with Gatekeeper Yes
GateKeeper IP Address 172.20.10.91
GateKeeper ID MoCS1000S
Gatekeeper Redundancy No
* Fallback to Internal Routing No
Gateway Registration Type H.323-ID
Register as Terminal No
Enable Mapping of Alias Number No
* Filter Calls To IP No
Enable RAI No
* RAI High Threshold 90
* RAI Low Threshold 90
RAI Loop Time 10
Gatekeeper Timers:
Registration Time [sec] 60
RAS Response Timeout [sec] 1
Number of RAS Retransmission 6
* Time Between GK Retries [sec] 60
* Coder Name (msec)
* 1st Coder g711Alaw64k 20
* 2nd Coder g729 30
* 3rd Coder
* 4th Coder
* 5th Coder
DTMF and Dialing Parameters
* Rx DTMF Option All
* 1st Tx DTMF Option RFC 2833
* 2nd Tx DTMF Option H.245 User Input
* 3rd Tx DTMF Option H.245 Signal Method
* 4th Tx DTMF Option Q.931 Info Message
* 5th Tx DTMF Option Not Supported
Page 1 of 3
08.06.2005

http://172.20.10.11/H323ProtocolDefinition

* RFC 2833 Payload Type 96
* Hook Flash Option H.245 User Input
* Max Digits In Phone Number 24
* Interdigit Timeout [sec]: 2
* Digit Mapping Rules:
* Use '#','*' Digits for Dialing Yes
* Dial Tone Duration [sec] 16
Number Manipulation and Routing Modes
* Add Hunt Group Id as Prefix No
* Add Port Number as Prefix No
* IP To Tel Routing Mode Route calls before manipulation
* Tel To IP Routing Mode Route calls before manipulation
IP->Tel Remove Routing Table Prefix No
H.450 Supplementary Services
Enable Hold Yes
Enable Transfer Yes
Enable Call Waiting No
* Number of Call Waiting Indications 2
* Time Between Call Waiting Indications 10
Enable Call Forward Yes
Misc Parameters
* IP Security No
* Channel Select Mode By Phone Number
* Enable Busy Out No
* Enable Caller ID No
* Caller ID Type ETSI
* Polarity Reversal No
* Enable Current Disconnect No
* Enable DID Wink No
* Send DTMF over H225/Q.931 No
Release Call on "Setup Ack" No
* Does Setup Include Phone Number? Yes
* Default Destination Number 1000
* Number of Max Calls 24
H.323 Base Port 0
H.225 Listen Port 1720
H.225 Dial Port: 1720
* Enable Q931 Cause Yes
* Enable Alt Routing Tel2IP No
* Alt Routing Tel2IP Mode None
* CDR Report Level End Call

 

[dlesap]

ooopps...

Thread 798-1031625

 

[ELBeast]

I don't think this is an issue with the ATA, I have gone over all the settings in the box. How do I change the TGAR? It is currently set to 1 which I have read from some documentation "The default of (1) automatically blocks direct access." So how do I change the TGAR and what would I change it to?

 

[3tdp33ler]

You can change trunks one by one:
LD 14
REQ chg
TYPE IPTI
TN the_tn
..
..
TGAR 0 <-- "0" means no TGAR/TARG restrictions

Or delete all H323 trunks at once:
LD 14
REQ del NN <-- NN is a number of trunks to delete
TYPE ipti
TN the_first_tn
..

and then restore them with correct TGAR:
LD 14
REQ new NN

 

[ELBeast]

Well it did turn out to be an issue with the ATA itself. The issue is the way it sends its digits. It kept sending them like it was calling an extension instead of in the E.164 format. I ended up creating a work around in the Succesion itself to get it to work. While this might not be the best way configure this, it does work and if anybody knows a better way I am definitely all ears...

I changed the NCOS of our H.323 virtual trunks, to allow for making outgoing calls.
Then in the NRS, under the gateway endpoint of the Signaling Server itself, I created a Level0 regional CDP.udp routing entry (80) with a route cost of 1.

Afterwards I went into Element manager and I created DSC 80; pointing to RLI 50, which I also created in Element manager. RLI 50 has a DMI (50)(Digit Manipulation Index) associated with it, which will delete the first two leading digits and then inserts a 9 thereby getting the call into BARS/NARS. So basically instead of dialing "9" to make a call out to the switched circuit network (public teleco network). I have to dial 80 and then whatever phone number to make a call to the outside world.

I modified the DialPlan field in the ATA with this entry:R80^(911|.r3)|X(1900|1976)|F011 . What it does is it automatically adds 80 to any number dialed except if the number dialed is 911 or the number dialed is only four digits. This allows me to retain extension to extension calling since we use four digit extensions. This string also blocks any dialing of 1900 or 1976 numbers and disallows fowarding to international numbers.


**On a side note, it appears that the first ATA I was testing with was faulty. It would just lose connectivity, the network LED would flash but I couldn't ping the device and it would unregister with the gatekeeper. It was a real pain because everytime I would try to change a configuration field via the web interface and apply the change, it would stop responding. I would then have to unplug it, wait between 5 to 10 seconds and plug it back in to get it working again. Luckily we had bought another device for testing and with which I swapped out and it seems to be working much better. I guess I should of tried that first instead of spending countless hours researching if there was a flag or a setting I could change that would solve the problem. I actually thought it was a type of power saving mode or something, LOL! Ah well, it least I have a better understanding of the ATA 188, the Succesion and how H.323 works now!**

 

[ELBeast]

Oh, this was using ATA 188 software Version: v3.1.2 atah323 (Build 040927A)
in case anybody cares; at the time of this writing it is the latest and greatest for the H.323 image...

 

[SL1User]

Could anybody post the settings of an ATA188 working on an cs1000M in H323 configuration?