Answer External SIP calls

From PBXes

(Difference between revisions)
Jump to: navigation, search
Revision as of 00:25, 11 June 2009 (edit)
bobpaul (Talk | contribs)

← Previous diff
Revision as of 18:33, 26 December 2009 (edit) (undo)
sipke (Talk | contribs)
(Answering SIP Calls)
Next diff →
Line 3: Line 3:
One of the defined features is answering calls to account-name@pbxes.com. This is actually slightly more advanced than simply that. One of the defined features is answering calls to account-name@pbxes.com. This is actually slightly more advanced than simply that.
-First off, all calls to account-name@pbxes.com will come in as incoming calls and get processed by your inbound routes. If you don't have a route that matches all calls (ie, trunk and CID blank), or the address you define (see example), you won't receive these calls.+First of all, calls to account-name@pbxes.com will come in as incoming calls and get processed by your inbound routes. If you don't have a route that matches all calls (ie, trunk and CID blank), or the address you define (see example), you won't receive these calls.
Extensions are private. This means calls to <account-name>-<extension>@pbxes.com will look the same, by default, as <account-name>@pbxes.com calls. The following example illustrates how to set up this function: Extensions are private. This means calls to <account-name>-<extension>@pbxes.com will look the same, by default, as <account-name>@pbxes.com calls. The following example illustrates how to set up this function:

Revision as of 18:33, 26 December 2009

Answering SIP Calls

One of the defined features is answering calls to account-name@pbxes.com. This is actually slightly more advanced than simply that.

First of all, calls to account-name@pbxes.com will come in as incoming calls and get processed by your inbound routes. If you don't have a route that matches all calls (ie, trunk and CID blank), or the address you define (see example), you won't receive these calls.

Extensions are private. This means calls to <account-name>-<extension>@pbxes.com will look the same, by default, as <account-name>@pbxes.com calls. The following example illustrates how to set up this function:

   Incoming Route
      Trunk: username-salesdept
      CID Number: 
      
      Set Destination: Ring Group 2
   
   Incoming Route
      Trunk: 
      CID Number:

      Set Destination: Ring Group 1

Here calls to username-salesdept@pbxes.org will go to ring group 2, but all other calls will go to ring group 1.

If you're having trouble, try using the IP address (217.195.32.11) instead of the domain name. For example, pbxes.org did not work in my tials, but pbxes.com and the ip address both worked.

Information taken this forum post