Very Computer

I am (desperately) trying to get some information on registering the cisco
ATA 186 analog adaptor on a Call Manager.  So far, I'm not having much luck.
I can't find a shred of documentation on Cisco's site about it & the docs
that came with the ATA & Call Manager don't get in to it.

If anyone here has done work with either products, I'd appreciate hearing
back from you!

Here's what I've done so far:

ATA Config:

Gateway = IP of Call Manager
UseLoginID = 1
LoginID0 = 1000 (the extension number of the phone)
UseSIP = 0

(These are the only settings I've changed on the ATA trying to get
registered on the Call Manager - there may be more, that's why I'm posting
here :-)

Call Manager Config:

Have created an H.323 gateway
Have created a device entry for the phone
Have created a user & associated the device / extension (1000) with that
user
Have created partitions
Have created route filters
Have created a route group
Have created a route list
Have created a route pattern

(Once again, there may be more, but these are the things I expected to
configure to get it to work).

So, here's what happens.  When I try to use the ATA I get dial tone.  If I
dial ext 1000 (my extension), I get a fast busy signal - I would expect
that, since the extension is in use.  I have also created another extension,
1001, & associated it with another device.  If I dial 1001, I get dead air -
no fast busy, no busy, no operator message, no gfy - no nothing.

Watching the h.323 graphs in the Admin Serviceability Tool, I see no
attempts or active h.323 connections.  The device properties for the phone
also says that the phone wasn't found.  They're both on the same test
network, communication between the two isn't an issue.

If anyone has any info they could share, I'd really really appreciate it.
I've been working on this for a while now & I'm about to pull my hair out.

Thanks!!!!!

The ATA with at least version 2.12 firmware works with Call Manager
3.0(10) and later as well as 3.1.

The ATA is basically an SCCP (Skinny Client Control Protocol) client
to Call Manager.  In Call manager versions 3.0 and 3.1 you basically
add the ATA as if each line on the ATA was a 7960 phone using using
the MAC address of the ATA for the FIRST line appearance. For the
second line appearance it is a little trickier.  To add the second
line appearance you need to do the same thing (add another 7960), BUT
take the MAC address of the ATA and drop the leftmost 2 digits of the
MAC and add '01' to the end.  For example, if the ATA had mac address:
AB.CD.EF.GH.IJ.KL then that would be the MAC you would use for line 1,
and for line 2 you would use CD.EF.GH.IJ.KL.01

Thats it.
HTH,
--C

or the second line appearance,  This can be done statically or with
auto registration.

On Thu, 17 Jan 2002 18:06:56 -0500, "Michael Fitzgerald"

Quote:> Michael,

> The ATA with at least version 2.12 firmware works with Call Manager
> 3.0(10) and later as well as 3.1.

> The ATA is basically an SCCP (Skinny Client Control Protocol) client
> to Call Manager.  In Call manager versions 3.0 and 3.1 you basically
> add the ATA as if each line on the ATA was a 7960 phone using using
> the MAC address of the ATA for the FIRST line appearance. For the
> second line appearance it is a little trickier.  To add the second
> line appearance you need to do the same thing (add another 7960), BUT
> take the MAC address of the ATA and drop the leftmost 2 digits of the
> MAC and add '01' to the end.  For example, if the ATA had mac address:
> AB.CD.EF.GH.IJ.KL then that would be the MAC you would use for line 1,
> and for line 2 you would use CD.EF.GH.IJ.KL.01

> Thats it.
> HTH,
> --C

You know, this whole time I've been running firmware 2.12 (CM v3.12c) & I
could not figure out how to get the darn thing to register.  I had the call
manager wide open w/ auto registration, but it just wouldn't work.  Of
course, from what you've told me, you've got to use SCCP - which I find out
requires firmware 2.12.ms.  Go figure.  Okay, so I've got that on & I've got
the ATA registered on the Call Manager.  Guess hurdle one has been cleared.

The only bad thing about having to use that firmware is that it doesn't
support SIP.  I only have one ATA right now, & I've been using it mainly for
IP to IP calls, which I need SIP for.  I guess if I can ever get the Call
Manager working properly, that'll be a non-issue.  We can all just register
with that.

I'll be frank with you, I've been working with data for a long time - this
voice stuff doesn't make a lot of sense to me right now :-).  Nothing like
being a newbie again!  I've combed through the cisco docs on the call
manager - do you know of any good non-cisco sites describing (clear english
if possible) the best way to go about setting up partitions, route plans,
etc.?  If you do, that would be great.  Or, if I had further questions,
would it be appropriate to post them here?  Not sure how many of you do
voice.

Thanks again for the nudge.

Quote:> Greetings!

I have one additional question about all of this.  ATA & Call Manager...

Up to this point, I've been using the ATA to make IP to IP calls.  The ATA
sits behind my firewall & I've been able to use is successfully by
forwarding ports 5060 & 10000 from the firewall to the ATA.  Diagram would
look something like this:

+---------+       +------------+
|Internet +-----+Other ATA |
+----+---+       +------------+
       |
+----+----+
| Firewall  |
+----+----+
       |
+----+-----+
|  My ATA  |
+-----------+

Now, I've upgraded the ATA firmware to 2.12.ms so I can register on the Call
Manager.  Consider this diagram:

+---------+
|Call Man|
+----+---+
       |
+----+----+      +------------+
| Internet +-----+Other ATA|
+----+----+      +------------+
       |
+----+----+
| Firewall  |
+----+----+
       |
+----+-----+
|  My ATA  |
+-----------+

Is this possible?  Being able to register a phone behind the firewall with
the call manager?  I don't think the registration would be a problem, but
the 2.12.ms firmware doesn't seem to have an option to specify the ports the
ATA listens on.  Will the previous 5060 & 10000 still work, or will this not
work at all??  Is there a better way of doing it???  How will the Call
Manager know where to send the call back to?

Thanks.

As to non Cisco web site docs for CM, the only thing I can think of is
the Cisco Press book "Call Manager Fundamentals"

The pain of setting it up should disappear in CM 3.2 from what I hear.

--C

On Thu, 17 Jan 2002 21:03:30 -0500, "Michael Fitzgerald"

I'm interested in setting up call manager ect so I me and my friend can use it
instead of using IP Dialing.

If you could email me that'd be great :)