Search results for query: *

Thanks! Although I was secretly hoping this to be the issue.

I am sorry I do not have the answer to your question. but rather a quick question of my own for you. Could you check under "display System-par special" and see if you have the SA8507 option set to yes in your system? i am trying to troubleshoot a problem and think this might be the route of it.

I have been searching the Net and found this... Some of the documents mention that the Avaya 8700 needs a certain feature turned on. SA8507..."H245 Support With Other Vendors?" Mine is set to "N". Where some of the doc's say it needs to be set to "Y" For those that have this working...

I have been searching the Net and found this... Some of the documents mention that the Avaya 8700 needs a certain feature turned on. SA8507..."H245 Support With Other Vendors?" Mine is set to "N". Where some of the doc's say it needs to be set to "Y" For those that have this working...

Did you ever figure this out? I am seeing the exact same problem...

Well it didn't help. Still unable to call from the Cisco to the Avaya equipment. This is really getting stupid. I am sure it is some thing really small.

Well it worked as far as being able to trace route. Open up your Services and look for a service labeled "Cisco Security Agent". Just stop it, (It will ask for authentication) and then try the trace route. Mine worked right away. I still do not know if that solves my main problem though of...

There is no way to block those numbers. But what you can do is set up a place for them to default to. (Like the receptionist) I think if you look at the first page of "ch sys feat" look at the DID/Tie/ISDN/SIP Intercept Treatment:...I think that is where calls go for unassigned DID's.

Cisco Security Agent...found it! So if I turn it off I can now place a trace route to the CCM. I will have to re-set up my lab and see if I can make calls from thh Cisco to the Avaya with that off.

What is CSA?

NO! And it is driving me nutz. Where I am at currently is that Cisco is looking into why the Call Manager will not respond to the trace route. They asked me for a packet Capture on the router so I supplied that late last week. I will let you know what they say.

Did you ever fix this? I am having the exact same issue.

i started and stopped the Protcol manager. That didn't change anything. I did switch from CDR2 to CDR1 and I am getting data now but it is not the unformatted tpye I am asking for. i look at teh raw data and i see leading digits that are messing up my database! I checked in cha sys...

Right now it is set to "Y". What does it do if I set it to "N"?

Yes it comes up fine.

Using eCAS through a CLan card. I have rebooted the server a couple of times. I also went into ch sys cdr and deleted/saved and re-added/saved teh endpoints...which I saw in another thread. I can ping the CLan card fine.

I show that my CDR Primary link is down. The buffer is maxed at 100%. The secondary shows as active. I have tried busying out the CDR link as well as the Data ext. Nothing seems to be working. How can i get this back up?

I opened a ticket with Avaya and they called in and tried to run a Trace Route to the Call manager. It will not complete. it fails after the first hop. They said this needs to be fixed and wouldn't do anything more with me until it is fixed. I pulled the Call Manager offline and placed a...

I have been working on this off and on for a while. After talking with Cisco for about 3 hours they ran a trace from the Call Manager. They say they are setting up the call and sending a "set-up" message to the Avaya 8700 but it is not responding to the request so it times out. Any thoughts?

I have been fooling with this for a while now. Still no progress. I opened a TAC with Cisco. After looking at the trace files they are telling me that the Call manager is setting up the call correctly and sending a "set-up" message to the 8700 but the Avaya is not responding. Anyone run into...