Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
routing to PBX RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm trying to place calls from MOC to a PBX phone using extension dialing (5 digits).  The call is denied and the OCS SipStack log shows "404 No matching rule has been found in the dial plan for the called number".  I do have a matching route for the 5-digit PBX extensions that points to the mediation server, but it doesn't look like the call reaches the mediation server.  I then added a normalization rule to the location profile that matches the 5-digit PBX extensions but doesn't modify the number, i.e., stays 5 digits.  After this however, I could not enter the 5-digit PBX number in the MOC (looks like MOC tries to resolve the number to a contact, finds nothing, and returns a "No results found") and could not dial.

     

    Is adding a normalization rule the right approach?  If so, how should it be configured?  If not, what else should be configured? 

    Thursday, July 19, 2007 10:21 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    You will still need the normalization rules. I would set it up to normalize to your 5 digit extension and test out.

     

    Monday, August 13, 2007 7:03 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    The normalizaiton rules are the right way to go. You need to have normalization rules that normalize the dialed number to the E.164 format. for example: +12345678901
    Monday, July 23, 2007 8:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Do I need to normalize every number to E.164?  If so, is there a way (in Routes or mediation server or other places) where I can undo the normalization before routing the call out of OCS?

     

    If I don't need to normalize every number to E.164, then how do I configure OCS to route out non-E.164 numbers?     

    Tuesday, July 24, 2007 1:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Your SIP to PSTN gateway will be expecting E.164 numbers as well. Why would you not need E.164 numbers?

    Monday, July 30, 2007 9:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm not trying to route to a SIP/PSTN gateway.  I'm trying to route to a PBX, that is why I wanted to preserve the extension dialing.

    Tuesday, July 31, 2007 1:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You will still need the normalization rules. I would set it up to normalize to your 5 digit extension and test out.

     

    Monday, August 13, 2007 7:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I did originally have a norm. rule that basically just matches the 5 digit extension and does not modify it.  However, the call still failed (see the first post in this thread).

    Wednesday, August 15, 2007 1:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

     

    In the User's Tel URI, you have to introduce a E.164 format phone. If you don't do this, you can't make any call.
    Tuesday, September 11, 2007 11:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

     

    How would this apply to extension to extension calling?

     

    For example, my extension is 2001 and I want to ring a colleague on 2002. Would me E.164 numbers be +2001 and +2002 respectively?

     

    In this case I have no external access, so just extension to extension (i.e. no "real" numbers for the phones)

    Wednesday, September 12, 2007 6:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    May be you can do that or you can do +country code area code and the number. For exemple, I'm in Argentina - Buenos Aires and I normalized my number to +5411and my personal number.

     

    If there is a case that other partener don't have a MOC so you have to manipulate numbers over your GW to traduce the Normalized number to the company usual extension numbers

     

    Friday, September 14, 2007 1:02 PM