Incoming Caller ID on Extension calls

Looking a new feature "Incoming caller ID on Extensions" so direct outside calls to the Extension either can be be diverted to an other extension or to dial out sip calls.

This is feature is already there for Inbound routing and working nicely.

Can you please explain this feature in more detail?

Are you looking to reach a SIP URI by dialing an extension number?

I am able to excess Extension by dialing SIP URI via DID provider. But extension does not have feature to match caller number like existing feature Inbound routing called Caller ID Number.
The work around is possible only if extension is shown as trunk and in Inbound routing then it is possible to used Caller ID number.

I tried to show Extension <my account name>-<this extension> and with only sip server 217.195.32.11. It did not work because Status Page shows Grey in color.

One of I-P-Tel moderator has mentioned before ". Additionally it is possible to make particular extensions reachable from outside. You need to add inbound routes therefore. As trunk name enter the public address you want to be reachable at, e.g. <account name>-<extension no> or <account name>-<arbitrary name>."

If extension can be registered as a Trunk , then extension caller ID feature will be redundant .

An inbound call to a DID or SIP URI, which has a specific CallerID number arrives at PBXes, and via an Inbound Route can ring a specific extension.

The above scenario is possible today, but I believe it is not what you are looking for. Are you looking for that call which rang the extension to be diverted to another extension based on the CallerID of the extension?

What is exactly the call scenario you are trying to achieve and what is its' benefit? Is this call scenario related to an outgoing or incoming call originally?

You are right to guess,as you stated looking for that call which rang the extension to be diverted to another extension based on the CallerID of the extension?
For sure it for incoming calls.

So a call comes in to your account and rings on extension A first, but then needs to be diverted to extension B based on the Caller ID of extension A, not the CallerID of the incoming call.

Now that we got to what you have in mind, can you please explain the case for this feature?

Will the call be picked up at extension A first, and then be transfered to extension B? If not, why wouldn't the call go to extension B directly? What is the case for ringing extension A first and then get transferred to extension B, based on extension's A CallerID?

Actually I want to transfer incoming calls to the extension based on caller ID to different VOIP. Let us say for simplicity I have 2 VOIP account and for 2 different incoming numbers.

At present all caller to the Extension will be transfered to only one specific VOIP using Dial feature in the Extension or in this simple case for 2 users each one incoming calls to 2 different extension to forward to 2 different VOIP.

But if extension recognize caller ID number then you can have multiple extension with known incoming caller ID number and then transfer each one to the respective VOIP.

This will solve the problem for DID calls which can be mapped to any one of Extension and the route the incoming calls to Extension based on Caller ID to different provider.

If I understand this well, you want to route inbound calls to DIDs via an Inbound Route to an extension which dials a SIP URI.

Will the routing decision of the incoming calls be based on their CallerID number?

Yes,the routing decision of the incoming calls direct to the Extesionbe to be based on their CallerID number.

This post has been edited 1 time(s), it was last edited by mon on 04.02.2008 at 21:03.

You should be able to achieve this via Inbound Routes. In case you need help on setting it up, you can click on the Support link.

This is the only way to work around to achieve via inbound routes and it is working and thanks for the support.
But nevertheless, it will be nice to have CallerID number feature in extension to avoid this work around.

Distinction between a PBX and a B2BUA

Extensions are meant to deliver calls to SiP User Agents or SIP URIs, not to route calls like trunks do. No routing decisions should be made based on the CallerID of an extension.

Let's not forget that PBXes is a hosted PBX service, not a partitioned Class-4 soft-switch. As I have stated in another post, I believe in stretching the envelope but not shredding it. Will a commercial IP PBX allow that functionality?

Keeping the above statement in mind, let's propose features which are somewhat related to an advanced IP PBX, not a Class-4 soft-switch or B2BUA.