route via SIP TO header?

I have multiple DIDs with Callcentric in a single account - I asked them about how to use an inbound route per DID and they said this:

"If pbxes.com is able to route via the SIP TO header then you will have no issue with using multiple numbers under a single Callcentric account. Unfortunately, we have not tested pbxes.com and how it interacts with our service. Additionally, if you are able to forward calls directly to your pbxes.com account then you can create a call treatment to forward calls with the following format: “extension@ipaddress” (without quotes)."

So, my question is, do you support routing via the SIP TO header? I know the extention@pbxes.org should work - but just wondering about the SIP TO header.

Thanks!

Update: I'm failing at properly routing when callcentric's DID is forwarded to extension@pbxes.org as well :/ Hrmm... I will keep trying this weekend.

This post has been edited 1 time(s), it was last edited by cc on 05.09.2009 at 10:32.

RE: route via SIP TO header?

Let me rephrase your request, so I can ensure I understand it properly.

You have a Callcentric account, with more than one DIDs, and you wish to route each DID to individual destinations (extensions, ring groups, etc.)

If the above statement is correct, there is a fully tested method which currently works with Callcentric, but involves a couple of configuration changes on each side.

Have a good day.

RE: route via SIP TO header?

Hi Diafora,

Yes, that is exactly what I'm trying to do... and my attempts for proper routing thus far have failed.

DID1 -> RingGroup1
DID2 -> extension XXX

That's basically what I'm trying to accomplish.

Can you please point me to any documentation which may assist me... or tell me what I need to do here.

Thank you so much!

This post has been edited 1 time(s), it was last edited by Dia on 05.09.2009 at 20:08.

RE: route via SIP TO header?

SInce setting this up properly will involve exchanging account passwords, you better open a support request and confirm your PBXes and Callcentric credentials.

At the end of the operation you can change them again, to ensure your privacy.

Have a good day.

RE: route via SIP TO header?

Hi Diafora,

So, this isn't something that you can walk me through and maybe we can create a wiki page out of it? How many minutes of support do I need to buy? 15? What exactly needs to be done?

Argh... voip is hard!

Thanks!

This post has been edited 1 time(s), it was last edited by Dia on 06.09.2009 at 19:16.

RE: Multiple Callcentric routes

Please trust me on this, VoIP provisioning is not hard at all, compared with Class 5 (PSTN) provisioning.

If you ever count how many screens need to be accessed, in order to put in service a single fixed line or a mobile number on a Nortel, Lucent, Alcatel or Siemens Class 5 switch, you will conclude its' complexity doesn't even come close to VoIP's.

Getting back to the matter at hand, in order to set this up properly, we need to access both your PBXes and Callcentric accounts. Since we haven't looked into your PBXes account's structure, we are unsure on the numbering scheme you have used. Some changes are also required on your Callcentric account, which should match the details on your PBXes account.

If everything goes according to plan, and it should, since I have tested this on my Callcentric and PBXes accounts, this shouldn't take more than 15 or 20 minutes. If it works out according to your requirements, you can attempt to document it on the Wiki or the forum, since you will have access to the configuration in both of your accounts.

RE: route via SIP TO header?

Hi Diafora,

I figured it out last night and I will attempt to document what I did - can you please confirm if this is what you had in mind?

Assumptions: Callcentric - 2 DIDs on a single account - 1-333-333-333 & 1-555-555-555, pbxes account name: foo

1) callcentric: log in and go to preferences->did forwarding and set the forwarding number of 1-333-333-3333 to foo-1001@pbxes.org and forward 1-555-555-5555 to foo-1002@pbxes.org
2) pbxes: create 2 inbound routes - and this is the key - in the 'Trunk' field enter: foo-1001 and in the other foo-1002 (note: you can eliminate one of these routes if it is the same as your 'default' route)

Now you have the ability to route based in the DID that was dialed. It would be better if inbound routing could handle the SIP TO header instead of this - but this is good enough for now

Diafora, would you like to add anything?

Thanks!

(edited: updated per Diafora's comments)

This post has been edited 2 time(s), it was last edited by Dia on 14.09.2009 at 15:31.

RE: route via SIP TO header?

In reality I would like to subtract something.

This is certainly the way of achieving the required functionality, but the creation of additional Extensions is not required. Creating the Inbound Routes is enough, to route calls from individual DIDs towards separate pre-existing Extensions, Ring Groups, or Queues.

Is essence, you can eliminate the first step, as long as these "extensions" don't exist in your PBXes account.

Also, following your example with only two DIDs, only one additional Inbound Route is required, since the existing Inbound Route can be used, for calls destined to the first DID.

This post has been edited 1 time(s), it was last edited by Dia on 14.09.2009 at 15:33.

RE: route via SIP TO header?

Thanks Diafora! I have updated the post per your comments and it works great!