Thirdlane.com logo

Dialing form Different Trunk lines in the same tenat

Posted by ramesh on Wed, 04/28/2010
Forums
Thirdlane platform General Questions

Hi,

we are having offices in two different location. we have configured all the extensions on same tenat but

1) if any one call from 100 level then it should go through from 248 area code number.

2) if any one call from 200 level of extesions it should go through from 810 area code number.

Right now i have configured such a way that the 200 level extension users they need to put 7 before the 10 digit number ex: 7XXXXXXXXXX .... in the outbound rules i am removing the 7 and it is going through 810 lines itself.

is their any i can do if any one calls from 200 level of extensions can i route through 810 line with out dialing 7 before 10 digit number..

please help me on this issue..

Thanks
Ramesh

Submitted by eeman on Wed, 04/28/2010 Permalink

not without a whole ass load of not-so-pretty custom programming. call routing is always based on where you are going not where you came from. Now your asking for dialplan that stops to evaluate a parameter and return another value that is later used to determine what trunk to use. It sounds like you've bought the wrong kind of sip service (ie not wholesale) and your trying to avoid toll charges. If you're violating their terms of service and they find out about it they could cut you off without notice.

Submitted by ramesh on Thu, 05/13/2010 Permalink

Hi Erik,

Thanks for your reply.

sorry for the delay am not their all these days....

what is mean to say is we used to have same functionality on the other asterisk box ie PBXinaflash i used to create custom trunking. so that with that particular area extensions i used to route through the custom trunking. so that extensions with different area code will go through.

ex:

100 series of extensions belongs to Troy location. i used to assign custom-trunk1

200 series of extensions belongs to Kalamazoo location. i used to assign custom-trunk2

i used to create custom trunking for that so that 100 series for extension will not pick up the 200 series sip line.

please help me on this

Thanks
Ramesh

Submitted by eeman on Thu, 05/13/2010 Permalink

create a new tenant and put the 200 series extensions there.. problem solved.

the reason you had that features in pbxinaflash is because they moved those extensions to a different context... this is the EXACT same mechanics used by MTE to separate tenants. You cannot have 1 tenant in 2 contexts because its the contexts themselves that define the tenant. The act of separating them, by definition, creates a new tenant.

Submitted by ramesh on Thu, 05/13/2010 Permalink

hi,

Erik Thanks for your quick reply.

I can create the new tenant but only problem is that. The 200 series extensions are in the part of ring group ant queue with 100 series. if i create a new tenant how do i ring the 200 series of extensions along with the 100 series of extensions.

How can i handle in this situation..

Please Help me..

Thanks
Ramesh

Submitted by eeman on Thu, 05/13/2010 Permalink

mutually exclusive goals. your going to have to invest in some custom programming to achieve what you're looking for. Theres less obstacles in STE, but theres still a few obstacles. I still dont understand why you need 2 different trunks just because the callerID changed... thats a sign of a BAD design with your carrier more than a limitation of PBX manager.

You should be able to have one trunk to your carrier regardless of who freaking makes a call or what their callerid displays. This stinks of trying to put the wrong kind of service (service meant for an end-user) onto a wholesale application like MTE.