Jump to content

Dial extension on trunk


Tim
 Share

Recommended Posts

We have a client that has an old PBX they are keeping in place and a pbxnsip server for their roadwarriers. We have setup an Audiocodes Mediant 1000 with a T-1 trunk into the old pbx. Extension to extension calls between the 2 pbx's work without an issue.

 

Is it possible for them to dial into the AA and call an extension that is on the other side of the trunk with the M1k?

 

Tim

Link to comment
Share on other sites

Try to set a static registration in the registration tab of the extension at the bottom in contact field. Put the number and ip add the number and ip Address of the gateway like sip:1234@1.2.3.4

 

So the only way to do this would be to create phantom extensions for all the extensions on the other PBX? The pbxnsip server has extensions in the 7xxx and 8xxx range, the other pbx has extensions in the 4xxx and 3xxx ranges, and there are several hundred of them. Right now I have a trunk and a dial plan entry that routes the 3xxx and 4xxx over to the Audiocodes gateway.

Link to comment
Share on other sites

So the only way to do this would be to create phantom extensions for all the extensions on the other PBX? The pbxnsip server has extensions in the 7xxx and 8xxx range, the other pbx has extensions in the 4xxx and 3xxx ranges, and there are several hundred of them. Right now I have a trunk and a dial plan entry that routes the 3xxx and 4xxx over to the Audiocodes gateway.

 

 

Creating phantom extensions should definately work. There should be a way to write a script to make it easier. Not sure if there is an easier way to route trunk to trunk like you need to do.

Link to comment
Share on other sites

If the caller wants to call an extension, it is the best choice to use a extension for this on the IP-PBX. Then all the features that do exist for this application work nicely. The only workaround is that you cannot use a "native" SIP phone, but use a PSTN gateway to call the extension on a legacy PBX. So far so good.

 

The first catch is the setup. If you have hundreds of extensions, setting that up can be a major problem. But if you take a look at the XML files in the working directories it should be relatively easy to copy them into other extensions with a shell script.

 

The other catch might be licensing. If you have 600 extensions then that solution can become more expensive that a single trunk setup. But I would say this is a business problem, and you should try to make a special deal for this case.

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...