Answer external sip calls - Revision history

tchau: /* Answering SIP Calls */

tchau — Fri, 15 Jun 2012 01:50:42 GMT

Answering SIP Calls

←Older revision		Revision as of 01:50, 15 June 2012
Line 14:		Line 14:

	Incoming Route		Incoming Route
-	Trunk:	+	Trunk:gooleVoice
-	CID Number:	+	CID Number:9493284720

	Set Destination: Ring Group 1		Set Destination: Ring Group 1

simonmaddox: /* Answering SIP Calls */

simonmaddox — Thu, 29 Jul 2010 18:59:35 GMT

Answering SIP Calls

←Older revision		Revision as of 18:59, 29 July 2010
Line 21:		Line 21:
	Here calls to username-salesdept@pbxes.org will go to ring group 2, but all other calls will go to 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.	+	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 trials, but pbxes.com and the ip address both worked.

	Information taken [http://www3.pbxes.com/forum/thread.php?threadid=44&sid=3114125aef73040f6744d15add161c1a this forum post]		Information taken [http://www3.pbxes.com/forum/thread.php?threadid=44&sid=3114125aef73040f6744d15add161c1a this forum post]

sipke: /* Answering SIP Calls */

sipke — Sat, 26 Dec 2009 18:33:13 GMT

Answering SIP Calls

←Older revision		Revision as of 18:33, 26 December 2009
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:

bobpaul at 00:25, 11 June 2009

bobpaul — Thu, 11 Jun 2009 00:25:10 GMT

←Older revision		Revision as of 00:25, 11 June 2009
Line 1:		Line 1:
	== Answering SIP Calls ==		== Answering SIP Calls ==

-	One of the defined features is answering calls to account-name@pbxes.~~org~~. 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.~~org~~ 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 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.

-	Extensions are private. This means calls to <account-name>-<extension>@pbxes.~~org~~ will look the same, by default, as <account-name>@pbxes.~~org~~ 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:

	Incoming Route		Incoming Route
Line 21:		Line 21:
	Here calls to username-salesdept@pbxes.org will go to ring group 2, but all other calls will go to 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 pbxes.org	+	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 [http://www3.pbxes.com/forum/thread.php?threadid=44&sid=3114125aef73040f6744d15add161c1a this forum post]		Information taken [http://www3.pbxes.com/forum/thread.php?threadid=44&sid=3114125aef73040f6744d15add161c1a this forum post]

bobpaul: New page: == Answering SIP Calls == One of the defined features is answering calls to account-name@pbxes.org. This is actually slightly more advanced than simply that. First off, all calls to acc...

bobpaul — Thu, 11 Jun 2009 00:10:12 GMT

New page: == Answering SIP Calls == One of the defined features is answering calls to account-name@pbxes.org. This is actually slightly more advanced than simply that. First off, all calls to acc...

New page

== Answering SIP Calls ==

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

First off, all calls to account-name@pbxes.org 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.org will look the same, by default, as <account-name>@pbxes.org 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 pbxes.org

Information taken [http://www3.pbxes.com/forum/thread.php?threadid=44&sid=3114125aef73040f6744d15add161c1a this forum post]