Polycom issue

[Shawnzhang]

It's really weird. ACOD in my PABX is 9. When I use the polycom dial an external number, such as 963911234, the trace log indicated 963399112234 or 966399112334 or 96339112234 something like this.
Please help...

 

[x11tech]

post a trace

 

[Shawnzhang]

trace log indicates that dialed number is 1336xxx/1366xx/1136xx while the number exactly I pressed is 136xxx
weird.... pls help...

 

[acewarlock]

We need to see the Trace not what you think we need to see.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[trvlr1]

Older polycom phones suffered from echo problems like this when placed in rooms with hard walls or ceilings or even close to large windows. Try putting it in a smaller room with fewer hard surfaces and try it to see if it makes a difference.

 

[Shawnzhang]

beneath pls find the trak log, the exact number I dialed actually is 15821429748

DCH 7 UIPE_OMSG CC_RELEASE_RESP REF 000008FE CH 7 9 TOD 18:36:06 CK 8FECBB57

DCH 7 UIPE_OMSG CC_SETUP_REQ REF 000008FF CH 7 8 TOD 18:37:56 CK 8FF01B1F
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:61324803 NUM PLAN: E164 TON: LOCL
CALLED #:15882144299748 NUM PLAN: E164 TON: UNKNOWN

DCH 7 UIPE_OMSG CC_DISC_REQ REF 000008FF CH 7 8 TOD 18:38:00 CK 8FF03796
CAUSE: #16 - NORMAL CALL CLEARING

DCH 7 UIPE_OMSG CC_RELEASE_RESP REF 000008FF CH 7 8 TOD 18:38:00 CK 8FF03818

DCH 7 UIPE_OMSG CC_SETUP_REQ REF 00000910 CH 7 21 TOD 18:48:06 CK 9002B8D0
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:61324801 NUM PLAN: E164 TON: LOCL
CALLED #:158214297748 NUM PLAN: E164 TON: UNKNOWN

DCH 7 UIPE_OMSG CC_DISC_REQ REF 00000910 CH 7 21 TOD 18:48:10 CK 9002DD85
CAUSE: #16 - NORMAL CALL CLEARING

DCH 7 UIPE_OMSG CC_RELEASE_RESP REF 00000910 CH 7 21 TOD 18:48:10 CK 9002DDF0

pls help...

 

[Shawnzhang]

Is it a possibility that cabling issue cause this problem?

 

[x11tech]

While on the call, please do the following:

OVL000
> LD 80

. TRAD <ll cc>

In the above DCH messaging log you posted the CH 7 9 for the first call attempt would be TRAD 7 9, for the second call attempt, it would be CH 7 21.

Does the problem happen with any other phone in the building?

If the problem does not happen with any other phone in the building, then I would suggest (1) try plugging the polycom in to an analog line somewhere else in the building (specifically where you are not having the problem) and (2) try plugging another analog phone in to the line where the polycom is now.

Process of elimination.

 

[Shawnzhang]

The problem just happen on Polycom. When I plug an anlog phone to the port where the Polycom previously plugged in, dialing test on anlog phone is OK. And wherever the polycom plug in, the problem persist.....

 

[trvlr1]

Going back to my previous entry, just try muting the Polycom as you dial the number, this will stop the echo. This is a quick fix for this problem, the ultimate fix is to buy one of the new versions.

 

[curtismo]

What model Polycom do you have (analog, Nortel digital or Nortel-branded IP)?

If its analog, have you tried it on a analog line direct from telco? Maybe you have a bad keypad causing the sporatic number duplication.

 

[x11tech]

I'd recommend trying the line with another analog phone (non-polycom) to determine if the problem happens with a different type of analog device, and also try what trvlr1 suggested, mute the polycom during dialing.

If muting the polycom helps, or if it doesn't happen on another analog device, then the problem is related to the polycom. Replace the polycom.

If neither muting nor using another analog device fixes the problem, then the issue is either the cable run or the port.


I think trvlr1 is probably right on with this one though.

 

[johnpoole]

are you sure the acod is 9.. or is that ac1.. if it's ac one you may be looking at the dgt side of a call..

i have not seen 9 used as acod in 20 years..nfrl is not that flexable

john poole
bellsouth business
columbia,sc

 

[phonz1]

or maybe a bad dial pad on the polycom? problem seems to follow the polycom!

 

[Triton101]

I second trvlr1's post, I had the same issue, had to MUTE before before dialing.

What is happening is that the Microphone is picking up the DTMF tones and that is why you get 99 11 88 and so forth....

 

[tnphoneman]

It would be nice if some of you would read before posting. The gentleman already stated that an analog phone was tested on the same port and it works fine. I saw at least 2 posts after that statement saying to try an analog phone on the line.

Basic trouble shooting 101 KISS (Keep It Simple Stupid). PBX and line has been eliminated. The problem is with the Polycom set itself. As stated before it is 1 of 2 possibilities

1. Bad dial pad on the set. (Not Likely but Possible)
2. Set is picking up echo in the room. (this is the most likely as it is probably a small room with hard walls. Probably covered in whiteboard material.)

 

[trvlr1]

Polycom have handsfree sets, which I assume this is, therefore testing a standard analog phone is not making a valid test of the scenario. Also, this is a problem that older Polycoms were prone to having, not all other handsfree analog phones had this issue. Polycom has addressed this issue with their newer units.

 

[Johnthephoneguy]

Actually testing it with ANY analog device is sufficent to say the line/pbx is good. If I can plug a regular 500 set in that port and it works fine, it doesnt matter to me if the problem phone is handsfree, wireless, pink, purple, or dances, the line works.

JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[tnphoneman]

I someshat disagree, this is a valid test to see if the port is functioning properly and to narrow down the trouble spot. I agree with the older polycom issue and it has been addressed but the test is still valid for the functionality of the PBX. Testing the port with a standard analog device eliminates the PBX as a possible cause.

 

[acewarlock]

tnphoneman: They may have been reading the prior post and did not refresh there screen before posting a reply, so don't get so upset. and so far Shanezhand hasn't said if he has tried muting the mic onthe Poly to see if the echo is causing the problem.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.