Normilzation Rules and the Tanjay (Polycom CX700) phone RRS feed

  • Question


    I have a problem when dialing numbers from a Polycom CX700 Tanjay phone.  If

    I pick up the receiver or hit the speaker phone button and then start to

    dial a number, the phone dials after entering 3 digits.  I am not able to

    enter the rest of the number.  If I enter the number first and then hit the

    call button, the CX700 behaves like MOC on my PC and dials the number.

    I understand that when you take the CX700 off hook and dial the number, it

    uses its location profile's normilization rules to know when to start

    dialing. We use 3 digit extensions internally, so I have a normilization

    rule for 3 digit extensions.  I also have 3 more rules, for seven digit, 10

    digit, and Long Distance US numbers.  I know that the CX-700 is dialing

    after entering 3 digits because of the 3 digit normilization rule.

    If I delete the 3 digit extension normalization rule, the 7 digit rule seems to control things... so that If I try to dial 18606331234 the CX700 starts to dial after the first 7 digits, 1860633 is what is passed on to the gateway.  It seems that the first rule that matches the digits entered causes the CX700 to start dialing. 

    I would like to know what I need to do to be able to call both 3 digit extensions and seven or ten digit phone numbers from the CX700 phone in the off hook position.  Is it possible?

    Here are my 4 normalization rules, listed in the same order as defined in

    the Location profile:





    Wednesday, March 26, 2008 10:31 PM

All replies

  • Using the Resource Kit Route Helper tool (but not the properties sheet in OCS administration) you can disable "fast dial” for the 3 digit rule.  That will prevent the Tanjay from placing the call immediately after only 3 digits are entered.  You can also make the 3 digit rule a lot more specific (for example by specifying what the first 1 or 2 digits must be) so that it won’t be confused with the first 3 digits of a real phone number.

    We solved the problem of allowing 10 digit numbers to be dialed with and without the 1 in front by specifying that the first digit of the 10 digit number must be a 2-9.

    Thursday, March 27, 2008 2:59 AM
  • Thanks very much James... I really appreciate the response.  I will give the tool a try, it sounds like it will do the trick.

    Thursday, March 27, 2008 3:05 AM
  • I created a 3 digit extension rule using the route helper tool that is set up to not Quick Dial, and that now works fine.  I am now able ot dial seven didit numbers without the phone starting the call after I have enetred 3 digits. 


    The new problem is that the 3 digit rule is now ignored entirely, so that if I intend to dial 3 digits, and I go off hook, enter them and then hit the call button, or I enter them first and then hit call without going offhook, the 3 digit rule that should add the + to the number is not used and the call fails (becuase is it needs the +).  It seems that when I set a rule to not use Quick Dial, the rule is ignored entirely, it is not just removed from the list of rules available for quick dial.  Any thoughts?






    Thursday, March 27, 2008 6:33 PM

    We use ^([2-9]\d{9})$ to quick dial calls 10 digit calls that start with 2-9 while also allowing an 11 digit rule for calls that start with 1.


    Are you saying that OCS doesnt ignore the 3 digit rule, it places the 3 digit calls, it just fails to perform the digit manipulation to add the "+"?


    Does the 3 digit rule work on Communicator?

    Thursday, March 27, 2008 8:43 PM
  • Paul,

    I just figured this out with the help of MS.

    You need to click the 'No Quick Dial' checkbox...

    ...and THEN go to the raw tab and remove the 't' by the '?'.

    This should allow the Tanjay to use the rule, but disable the quick dial.



    Thursday, May 15, 2008 3:59 AM