locked
Normalize CallerID? RRS feed

  • Question

  •  

    Does anybody know how to normalize the Caller ID to e.164.

     

    For example, my Cisco GW does not support "+" so the Caller ID ( 234 567-8901) comes through as 2345678901. I can transform the digits within the gateway to include the 1 but not the "+" and OCS cannot match the reverse lookup to identify the caller ID.

     

    Has anybody dealt with this issue. The dialogic gw's support the "+" and thus it works well but - we are a cisco "only" shop and that is what may end up being purchased.

     

     

    Rick Phillips

    University of Kentucky

    Monday, March 3, 2008 6:04 PM

All replies

  •  

    I had the same problem with our CISCO CUPS server and

    did head in before I got it right.

     

    The trick is to match your Server URI with your Line URI phone number:

     

    eg.

     

    Server URI    sip:34763@abc1cup001.domain.com

    Line URI       tel:34763;phone-context=dialstring

     

    Make sure the phone number in the telephone attribute of AD has a + in front of it and your Norm rules have to be spot on.

     

    Thursday, March 27, 2008 4:07 AM