Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Normalization issues RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    Hi

     

    I'm having problems with the phone number normalizations. I'v read the Voice planing guide but in my case it does not work.

     

    I'm living in the Netherlands so our country code 31 and my area code is 0181 (181).

    I have couple of users in AD with the mobile numbers like +31612345678 the mobile number begin mostly with 6.


    I can see this number on my CX700 phone of the contact.     I also created a normalization for this number like ( ^\+31(\d{9})$ ) and translation pattern 0$1 so the mobile number +31612345678 translates to 0612345678.

     

    On the Routes tab I defined a route for all calls with .*

     

    My mediation server is also the gateway and it's connected directly to the ISDN network.

    The problem is that numbers beginning with + wil cause call error and no normalization. If I check the call logs of my gateway the called number is 31612345678 and that is wrong. It must be 0612345678.

     

    In the normalization page if I test the +31612345678 it will normaliza it without problems. But if I want to make call with the tanjay or with the Voip Test Set software the number will not be normalized.

    I also test this with the Enterprise Voice Route Helper. If I type the number +31612345678 then I'm getting the following error "The client side normalization caused a different location profile to be used on the server. The server location profile is: dialstring"

     

    By the way the are code (181) is not for the mobile numbers.

     

    Second question. I'm going to attach the gateway tou our PBX. We have internal 4 digit numbers with no public phone numbers for the staff, the incoming calls are routed by the dispatch. do I need to convert those 4 digit number to E164? So yes, is this ok +1234 country and are code is a little strage beacuse it is internal. and I dont want that the staff must dial like 31 181 1234 I just want 4 digit.

    Whats going on here?

    Help is welcome.

    Wednesday, December 5, 2007 11:44 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    Hi Oguz,

     

    In your normalization rules you should implement how to get the number into E.164, such that all calls within OCS uses E.164 numbers. Using E.164 enables you to have uniform routing throughout OCS. On the break-out points from OCS, i.e. the media gateways, you also need to implement normalization and de-normalization.

     

    The media gateway needs to be able to take a number in E.164 and normalize it such that it can be sent out to the PBX/Public PSTN. Typically it means removing +<cc> (in your case +31) and maybe replace it with 0. It could also be replacing + with 00 to dial internationally. Along the same lines incoming calls needs maybe to have 0 stripped and +31 added or have 00cc converted to +45.

     

    So in summary: make sure you use E.164 within OCS and at the break-out point convert/normalize to the conventions of the recipient (PBX/PSTN). Remember to do this both or Calling and Called Line Id.

     

    For your second question yes use E.164. With normalization rules you can enable the staff to keep dialing only 4 digits in both systems. Again on the media gateway implement the needed conversions.

     

    best regards

       Jens

    Wednesday, December 5, 2007 1:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

     

    De-normalization is not possible on my gateway. I have build the gateway with Divar Server 4BRI-8M and Sipcontrol. The Gateway must receive the exact to call number. If I call the follwing number. 010 1234567 with the phone pattern expression ^(\d*[0-9]{10})$  I can make calls to the number that I dialed, it will be passed directly without converting it into E164. This works just fine actually.How is this possible? Only if I enter the phone number of a user in AD with E164 style the number will not be dialed. So that's why I created the ^\+31(\d{9})$   0$1  to remove the +31 and add the 0 to the number.

     

    The pattern expression gives me no errors on that expression. Only when I try to call the translated  number it does not corresponds with the translated number, it's dialing 31612345678 while translated number is 0612345678. You can see it below.

     

    http://www.whatsup.nl/norm.jpg

    http://www.whatsup.nl/norm2.jpg

     

     

     

     

    Wednesday, December 5, 2007 1:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Please consult the product documentation or contact Dialogic to get support on how to configure the de-normalization. I know that it is possible to do it for connections to PSTN in other countries in Europe.

     

    best regards

       Jens

     

    Wednesday, December 5, 2007 2:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    this a bit OT.

     

    is there a way to normalize an incoming call from a gateway? lets say, if the gateway is throwing a dialed number (i.e 990) is it possible for the mediation server to normalize it so the the front-end server will see +990.

     

    thanks!

     

    kent

    Wednesday, January 9, 2008 9:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes. You configure a Location Profile on the Mediation Server. If the number is not normalized when the Mediation Server gets it it will use the location profile to normalize it.

     

    best regards

       Jens

    Wednesday, January 9, 2008 5:01 PM