OTM and PUA

[technickelone]

Anyone had any issues with OTM after upgrade to Succession?
If i make any changes to a phone it changes the Pickup to denied PUD. It works from the host but my client has been reloaded and still has the issue.

 

[johnpoole]

tested the otm here and it does the same thing unless i have a rnpg assigned, guess it's a good thing that i don't use it.. seems to work fine for smaller switches and i do know of a user with 2 81's that uses it full time, i'll stick with command line, when i mess up it's one phone at a time..

john poole
bellsouth business
columbia,sc

 

[technickelone]

That is so strange. I give it a rnpg and allow but it still doesn't take. We updated OTM Friday night to let it know its Succession now and I think thats when it started but not sure.

 

[sandyml]

Do you have your OTM updates (peps) installed? This has been a known problem unless you do so.

 

[NortelGuy1979]

SandyML - we use OTM and just upgraded; we aren't haveing this problem (I don't think) but I know we did not install any PEPs. Do you have a list of them? Thanks! -M

Matt H.
TMC - KCMO, USA

 

[johnpoole]

might need a few patches..

00 MP05829 Core p12511_1.cpt
01 Q00464575 BRIL/BRIT p16540_1.cpt
02 Q671307 QSIG p17448_5.cpt
03 Q00689616 ACD/NACD p17512_1.cpt
04 Q00665199 CDR p17559_2.cpt
05 Q00702474 CORE p17571_1.cpt
06 Q00709405 Symposium p17643_1.cpt
07 Q00712182 Group Hunt/PLDN p17790_1.cpt
08 Q00349307 CORE p17820_1.cpt
09 Q00724590 TAURUS p17823_1.cpt
10 Q00757690 Meridian Mail p17825_1.cpt
11 Q00748087 Core p17845_1.cpt
12 Q00753247 CORE p17853_1.cpt
13 Q00743283 CORE p17889_1.cpt
14 Q00743414 CORE p17890_1.cpt
15 Q00749407 Core p17893_1.cpt
17 Q00761422 core p17895_1.cpt
18 Q00660652 Taurus Sets p17897_1.cpt
19 Q00761893 Core p17899_1.cpt
20 Q00754053 Core p17922_1.cpt
21 Q00771896 CORE p17946_2.cpt
22 Q00775297 Core p17960_1.cpt
23 Q00743121 CallPilot p18025_2.cpt
25 Q00755955- Core p18028_1.cpt
26 Q00779816 ACD/NACD p18040_1.cpt
27 Q00735881 CORE p18043_1.cpt
28 Q00769104 CORE p18051_1.cpt
29 Q00782006 ACD/NACD p18066_1.cpt
30 Q00790668 QSIG p18081_1.cpt
31 Q00767458 CORE p18090_1.cpt
32 Q00792920 ACD/NACD p18123_2.cpt
33 Q00798017 GF p18163_1.cpt
34 Q00773689 Core p18229_1.cpt
35 Q00828559 CORE p18242_1.cpt
36 Q00783145 p18250_1 p18250_1.cpt
37 Q828904 QSIG p18305_1.cpt
38 Q00744653 Core p18380_1.cpt
39 Q00792601 Symposium p18387_1.cpt
40 Q00811297 CORE p18393_1.cpt
41 Q00861684 QSIG p18433_1.cpt
42 Q00859329 Symposium p18444_1.cpt
43 Q00850201 CORE p18446_1.cpt
44 RAJARSHI H ACD/NACD p18677_2.cpt
45 Q00834606 p18739_1 p18739_1.cpt
46 Q00800638 p18875_1 p18875_1.cpt


john poole
bellsouth business
columbia,sc

 

[technickelone]

I'm not sure of any recent patches. But I have a ticket in with Bellsouth. How do I look at the patches in OTM

 

[technickelone]

Got it!!!
Go to Start - programs OTM and there should be a patch utility and then download any new ones

 

[Woodro]

I'm running OTM 2.1 and just put in patch 2105su2. I don't know if it covers that issue but I was told this was the latest patch from Nortel. My problem was on LDAP and mapping attributes.

Woodro

 

[sandyml]

Woodro, that is indeed the one for OTM 2.1. There is also a pep, 21056p17, concerning List Manager appearing to hang. If using OTM 2.2, there is a patch 22078su1 that should be applied.

 

[technickelone]

Yes, I just found that out.. su2 is the latest and I'm going to load it soon. Thanks

 

[Menk]

We ran across this issue where the change would work on the PBX but if you used OTM PUA was ignored and PUD was sent instead.

We used a patch SU 21056su2 for OTM 2.10.56 to resolve this issue.

 

[jimeec]

Same problem here with PUD/PUA after succ 3.0 upgrade to an 81c running OTM.Nortel patch was the fix.Just wanted to put my 2 cents in.

 

[sandyml]

It's a very common problem. A good reminder to always check for the latest updates and make sure you install them when you install the application.