Cisco ATA 188 with a CS1000 (Option 11C)

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

Reply to
Beast
Loading thread data ...

************************ I ending up figuring this out: I created a entry in the DSC with the digits 7059 (The DID) 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) 060320|11:28:38 CLIP 060320|11:28:38 SCC->(0 0) 060320|11:28:38 dial 060320|11:28:38 GK(0 0) 060320|11:28:43 SCC->(0 1) 060320|11:28:43 [0]StopTone 060320|11:28:43 SCC->(0 0) 060320|11:28:43 CCBS expired 060320|11:28:43 [0]MPT mode 0 060320|11:28:43 SCC->(0 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??

Reply to
Beast
************************* 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!**
Reply to
Beast

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...
Reply to
Beast

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.