Polycom IP 5000 busy signal when attempting to dial external lines

[Enticles]

Hi Folks,

I am having a bit of a battle with a Polycom IP 5000 for dialling externally.  calls to internal extensions work without issue, and external calls can route to the polycom via our auto attendant.

the last piece of the puzzle is configuring the polycom and our Mitel 3300 to be dial external numbers.  before we complete dialling we get a busy tone.

I have been experimenting with the digitmapping and have not had much success, i am beginning to wonder if there is a setting on the mitel controller that allows or disallows external dialling - I have not found one yet.

If anyone has any suggestions / advice that would be much appreciated.

[acejavelin]

This sounds like a dial plan issue... It is matching to X number of digits and sending, which is invalid. You may need to adjust the dialplan for your local dialplan

How are you dialing though? Usually if you dial the full digits then press SEND it works, or are you going off-hook and dialing the digits? With SIP you should always use the SEND button method.

[Enticles]

Hi Acejavelin,

I have tried using the send method as well as opening the line and dialling - unfortunately neither approach yields a better result.

What happens is i can enter the correct digits in the dialpad - which leads me to think the digitmap is correct on the polycom, however the call fails instantly and is met with a busy tone.

I have ran a CCS trace on the controller and tried dialling, and had the following come up:

15:27:25 RIL DPN PEER NIL_PEER_ 826 2C ISRM_I                                 
           ;10;*1#*19*Z#*58*Ca*1*Z#*100*Hangar 2 Breakro#                     
15:27:25 RIL DPN PEER NIL_PEER_ 826 2B SSRM_C                                 
           *58*CW*s]@s@@@@Dkgb`p#*50*8301#9<Masked For Privacy>                         
15:27:25 RO116 DPN 1F ISRM_I  ;10;*1*1#*50*8301#*58A*Cc*4*8301#               
15:27:25 RO116 DPN 1C SSRM_I  *100*HNGR2 Breakroom#*19*Z#                     
15:27:25 RO116 DPN 2D SSRM_I  *58*CW*s]@s@@@@Dkgb`p#*58*C6*001#*58*C4*4*1#     
15:27:25 RO116 DPN B  SSRM_C  <Masked For Privacy>                                     
15:27:25 RI116 DPN 23 CRM/CIM ;29;*100*ACCESS BARRED ACCESS BARRED#           
15:27:25 ROL DPN PEER NIL_PEER_ 826 23 CRM/CIM                                 
           ;29;*100*ACCESS BARRED ACCESS BARRED# 

A bit of googling and searching on these forums had lead me to suspect there may be a DID issue with our PRI provider, so i renumbered the extension from 8301 (outside of our paid DID range) to 8225, which would be within our paid DID range.  There was no change to the result.

Any ideas?

[acejavelin]

CCS Trace is rarely usable in this case... If we are talking about a PRI, then the relevant information would be in "EDT TRACE TSP L2L3 <PLID>" (remember this is a toggle on/off command, do not leave it on for extended periods, it won't hurt anything but can get very annoying later)

If the COR is correct and you believe the carrier is blocking your call, this will show it instantly.

[Enticles]

Thanks for that Acejavelin, I am really quite inexperienced when it comes to PBX's so i am trying to piece together the steps as I go.

I will likely get infront of the bothersome polycom this afternoon and give your command a shot.  I'll let you know how it goes, good or bad

[ZuluAlpha]

We have deployed some polycoms and there's a place in the phone itself you have to put a dialing plan I think.

[Enticles]

CCS Trace is rarely usable in this case... If we are talking about a PRI, then the relevant information would be in "EDT TRACE TSP L2L3 <PLID>" (remember this is a toggle on/off command, do not leave it on for extended periods, it won't hurt anything but can get very annoying later)

If the COR is correct and you believe the carrier is blocking your call, this will show it instantly.

Just got around to running the command, here's the result from a traced call:

 HDLC CC on link 1 trace enable .

 HDLC VERBOSE on link 1 trace enable .

10:28:12 RIL DPN PEER NIL_PEER_ 867 2C ISRM_I                                   
           ;10;*1#*19*Z#*58*Ca*1*Z#*100*Hangar 2 Breakro#                       
10:28:12 RIL DPN PEER NIL_PEER_ 867 2B SSRM_C                                   
           *58*CW*s]@s@@@@DndbCp#*50*8225#9<masked for privacy>                           
10:28:12 RO116 DPN 1F ISRM_I  ;10;*1*1#*50*8225#*58A*Cc*4*8225#                 
10:28:12 RO116 DPN 18 SSRM_I  *100*H.Breakroom#*19*Z#                           
10:28:12 RO116 DPN 2D SSRM_I  *58*CW*s]@s@@@@DndbCp#*58*C6*001#*58*C4*4*1#     
10:28:12 RO116 DPN B  SSRM_C  <masked for privacy>                                       
10:28:12 RI116 DPN 23 CRM/CIM ;29;*100*ACCESS BARRED ACCESS BARRED#             
10:28:12 ROL DPN PEER NIL_PEER_ 867 23 CRM/CIM                                 
           ;29;*100*ACCESS BARRED ACCESS BARRED#                               
 HDLC CC on link 1 trace disable .

 HDLC VERBOSE on link 1 trace disable .

the error (to me at least) looks very similar to the other trace i attempted to do, would i be correct in presuming the carrier is blocking this device from making a call over the PRI?

[Enticles]

Well, i caved and called in some help from our Mitel support vendor.

Turns out i had not configured the class of service correctly, despite being certain that i had.

calls are now routing externally without any further issue - happy days!

Thanks for your suggestions everybody!