Jump to content

Translate incoming calls to e.164


Coen
 Share

Recommended Posts

I'm having some trouble to translate incoming calls to the e.164 format.

My PBXnSIP installation is connect to OCS 2007 server with a mediation server in between.

 

I've created a PBXnSIP trunk to a Dutch VOIP provider (Budget Phone). The trunk is configured to forward all the calls to a user extension. (Send call to extension: 600).

 

When I call my Budget Phone number from a PSTN phone the trunk will accept the call and forward it to extension 600.

My communicator client will ring and is show the caller-id of the incoming phone call. This displayed number is not compatible with the e.164 standard. With means OCS is unable to do a reverse number lookup in AD or Outlook.

 

Can somebody tell me how to translate incoming calls to a e.164 standard before they are forwarded to OCS??

 

Greeting,

 

Coen

Link to comment
Share on other sites

I'm having some trouble to translate incoming calls to the e.164 format.

My PBXnSIP installation is connect to OCS 2007 server with a mediation server in between.

 

I've created a PBXnSIP trunk to a Dutch VOIP provider (Budget Phone). The trunk is configured to forward all the calls to a user extension. (Send call to extension: 600).

 

When I call my Budget Phone number from a PSTN phone the trunk will accept the call and forward it to extension 600.

My communicator client will ring and is show the caller-id of the incoming phone call. This displayed number is not compatible with the e.164 standard. With means OCS is unable to do a reverse number lookup in AD or Outlook.

 

Can somebody tell me how to translate incoming calls to a e.164 standard before they are forwarded to OCS??

 

That topic is pretty well addressed in 3.1. If you like, you have a preview image. What OS?

Link to comment
Share on other sites

I'm running Windows Server 2003 (32bit)

 

Check out http://pbxnsip.com/protect/. See http://wiki.pbxnsip.com/index.php/Installi...#Manual_Upgrade on how to upgrade. In this case, you should make a backup before doing this.

 

In the trunk, there is a setting that defines how to present the number. Choose the "+" style. You must also choose a country code in the domain so that the PBX knows how to interpret numbers.

Link to comment
Share on other sites

Check out http://pbxnsip.com/protect/. See <a href="http://wiki.pbxnsip.com/index.php/Installing_in_Windows#Manual_Upgrade" target="_blank">http://wiki.pbxnsip.com/index.php/Installi...#Manual_Upgrade://http://pbxnsip.com/protect/[color=&...#Manual_Upgrade on how to upgrade. In this case, you should make a backup before doing this.

 

In the trunk, there is a setting that defines how to present the number. Choose the "+" style. You must also choose a country code in the domain so that the PBX knows how to interpret numbers.

 

I have installed the lasted 3.1 build. After that I've configured the trunk settings (Rewrite global numbers: "+" style).

And also change the country code to 31 in the domain settings.

 

But it didn't solve my problem. Inbound call are still in the wrong format. (0351234567 instead of +31351234567)

Do I need to change the trunk settings of my VOIP provider or the one to the OCS mediation server?

Link to comment
Share on other sites

I have installed the lasted 3.1 build. After that I've configured the trunk settings (Rewrite global numbers: "+" style).

And also change the country code to 31 in the domain settings.

 

But it didn't solve my problem. Inbound call are still in the wrong format. (0351234567 instead of +31351234567)

Do I need to change the trunk settings of my VOIP provider or the one to the OCS mediation server?

 

Hmmm. Seems that this did not completely solve the problem. I guess we have to try this out here as well...

Link to comment
Share on other sites

  • 3 weeks later...

FYI:

 

After installing the latest versie (3.1.0.3043), the translation to the e.164 works!

When calling from a pstn line to my pbxnsip setup the call is translated to the e.164 format.

OCS is now able to do a reverse number lookup and showing the correct contact name.

 

I'm happy :D

Link to comment
Share on other sites

FYI:

 

After installing the latest versie (3.1.0.3043), the translation to the e.164 works!

When calling from a pstn line to my pbxnsip setup the call is translated to the e.164 format.

OCS is now able to do a reverse number lookup and showing the correct contact name.

 

I'm happy :D

 

Well, so we just have another reason to do this painful internal conversion into the global telephone number format!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...