Tenant to Tenant Dialing

So, is a tenant to tenant trunk not possible?

I'm confused as to why you would want this and if it was possible how would you deal with me being on 1 tenant ext 301, 2-3-4-5 other tenants having users also using ext 301, how would the system know which tenant you want to dial..?

why not just call the other tenant using the DID assigned..?

i can think of a specific reason why. Lets say a company has 3 offices but they want to 4 digit dial each other. Under most circumstances they operate as a single entity and for most purposes could in fact function as just 1 tenant, with the following exceptions:

callerID on outbound calls, perhaps they want to use a different callerID so that the DNIS matches a main number for that specific location, this currently can be set on a per-extension basis so it seems covered.

E911 calling, when each office dials 911 they certainly need the registered DNIS to be broadcast as the callerID so that the automated location database screen-pops the correct location to the PSAP.

I would suspect that if Emergency calling scripting were massaged just a little bit it would be possible to share multiple offices as a single tennant.

The last possible reason I have seen give way to seperating a company into multiple tenants is Directory(). Sometimes they want the Directory only to access people within one office versus a company-wide variant.

eeman

1) callID - this shouldn't be a problem as you stated..

2) E911 - if the out bound called ID is set per ext this also should be a problem as you can set the location on a per DID basis.

2) IF the someting is setup that each location is set on a different tenant, we are back to the org question.. not really possible for the reasons I gave above..

that being said, what we do for our res customers is we set and extension (4 digits) that they can dial that forwards to our IVR so they do not have to dial the hole 7-10 or 11 digits..

G

I have kind of a selfish reason for wanting to do this, and as I begin to understand it I wonder if it is going to more complex than it is worth.

My sole reason for wanting to do it is that I need to have an extension on two tenants, and I would prefer to have all calls come to the same extension. I can go the route of forwarding calls between tenants using DIDs, but I will have to pay for the DIDs and for the calls that hit my PSTN gateway provider (Telasip).

I thought that if I could go directly from tenant to tenant via a trunk that I define I could hand the calls back and forth without hitting the PSTN.

I have been looking for a good step-by-step HOWTO on how to set up a server to server trunk thinking that I would be able to follow it to do this, but nothing that I have found seems to be complete.

not sure what your using for your DIDs as it should cost more then pennies a month.

BUT what you could do is put in a SER server and make up a number for the system to use and have the SER server route all traffic for that number to a tenant or ext on a set tenant like a direct dial number..

other then that I have nothing.. and honestly if thats all you want.. pay the .99 cent a month

This is a big What If! What if you are growing a large customer base and more and more clients are coming on board. (That have a reason to call each other) As more and more clients come on board the calls between tenants would not have to hit the PSTN. If you were to process around 250000 minutes a month with client to client calls at .007 (+ / - ) per minute over the PSTN it could cost $1750.00 a month more to the termination provider.

So my question would be stated like this. How would Thirdlane MTE keep calls destined for the same server local.

Assumption 1: Build a route that matches a pattern for each of the DID's associated with the server?

* Outbound call is started from Tenant 15 destined for 555-555-5555 which is the DID for Tenant 67

* The call is caught by a route that keeps it in the server but hands it off to 67 No PSTN/SIP Provider needed.

Assumption 2: Is this done by having another server in front of the MTE returning the call to the originating server? Acting as a gateway?

Let me know your thoughts,

Regards,

Serverbeach

I use assumption 2. Every call is converted into E.164 format so that I dont have to double up on rules if someone dials 7 digits, 10 digits, 11 digits etc. If the number is a number I happen to host it remains on net.