Search results for query: *

Hi. we are attempting to set up in-house "broadcasts" to all (or groups) of cisco phones. Yes, there are "off the shelf" products for this, but they are not cheap AND we have already paid for this functionality (see below). This has been frustrating -- there is documentation on how to...

Hmmm. An interesting line of thought, StanleySteamer. I set PII = YES on my RDB entry - didn't improve things (but you did say this was for "incoming", ya?). I also looked (high & low) for *anything* resembling that in the Cisco world... with no luck. It's going to be something goofy like...

Yes: Cisco bad (and we have the sniffer traces to prove it). So here's another wrinkle on this same issue. When someone calls a DN that's MARPed on a set that is DDGA, but that DN is SCN'd on another set that is DDGD, the CFNA'd call over to UNITY has no called/forwarding number info (same as...

911guru : Bingo. Debugs on the Cisco PRI gateway CLEARLY show "Original Called Number" and "Redirecting Number" with the correct info in them (ie: the DN of the DDGD'd set)... yet when you look in Call Viewer on UNITY, those fields are blissfully-blank. Nice. Thanks - now we know which...

Hi. we have a largely successful Nortel (81C) integration with Cisco Call Manager. We recently moved everyone on the Nortel side over to UNITY for voice msg'g. Most things worked just fine with a little tweaking. Our UNITY pilot number (on the Nortel side) is an ACD with MWC=Yes and...

JcBWF : did you learn anything from your rep? Thanks, B

Has anyone got the webDialer working on CM 5.1.x ? We cannot seem to get it to recognize a "Calling device" for our users.

Ooops -- sorry to be the bearer of bad news, JcBWF ! B

John: (D-channel monitoring does not show whether I am sending names or not) The names are definitely coming across and appear on the Nortel sets OK... it's only the *called* number when a call is placed fron a nortel set to one on the Cisco side.

Yes, the garbage characters is a known issue for us (Cisco was up front about that). But there wasn't any mention that this might be linked to the ------ problem on the *calling* phone, though. Thanks, B

So presumably you would have this same problem if your tie trunk was Cisco -to- Cisco ? We are at: System version: 5.1.1.2000-2 The plot thickens: the "known good" site I was comparing my configs to is at 4.1.3 sr5b. Do you have any bug-IDs or anything I can throw at our local Cisco guys? (ie...

RCAP on both D-channels is: ND2

Hi. we have an odd problem. We have an option 81c on rel 25.30 with a couple of PRIs to Cisco router (2821) for integration with Call Manager (no Q.SIG. It is not an option for us). Locals on the cisco side are CDP'd on the 81c across these PRIs. Everything works fine, except when a Nortel...

Thanks 3tdp33ler. Sadly, not the answer I was hoping for, but thanks for responding. barbarian

Hi. in thread798-1294006 underwoj said that I was wondering if you needed the CCDR package (Calling line Identification in Call Detail Recording) to get this to work. Does anyone know? Thanks B

Aaaaaahh! OK. This is very definitely the flip'n switch type! Thanks, B

Hmmm... some docs describe procedures involving flipping switches & pressing buttons on the CP & CNI cards, while other docs talk about doing it completely in software from load 135 / 137. I'm not sure which is the correct way... B

Can anyone point me at doc for the correct procedure for split'g and doing a parallel reload on an option 81c? Thanks, barbarian

...so what is the relevance of "port #" then if we are only putting one PTY per DNUM?

OK. So that would be : dnum 14 port 0 dnum 14 port 1 dnum 15 port 0 dnum 15 port 1 Are those the correct steps in ADAN, ie: doing NEW TTY 14 (twice) for TTY 14, once with port 0, then again with port 1? Thanks, B