Thirdlane.com logo

question about call routing

Posted by Had on Tue, 01/20/2009
Forums
Thirdlane platform General Questions

Imagine you have 2 asterisk systems.
First is main gateway for billing and SIP and PSTN trunks termination and second is thirdlane MTE.
On MTE you have 2 customers.
First customer has number (example) 0208 3600412.
Second customer will call first on that number. Call will go from MTE box to gateway box and ...

Now the question is...

Will the gateway box reroute the call back to MTE box? Or will the call go out from gateway box to service provider and then come back?

Peter

Submitted by eeman on Tue, 01/20/2009 Permalink

that depends entirely on how you build your gateway box, my gateway box ensures that all my customer calls remain on my network.

Submitted by eeman on Tue, 01/27/2009 Permalink

Neither. Thirdlane dialplan is not compatible with CDR logging needed by billing software. Additionally the least cost routing engines I use, local number database, T.38 gateway software, and concurrent call count management, are all custom written applications to make my gateway asterisk box behave more like a phone switch and less like a PBX.

Submitted by Had on Sat, 01/31/2009 Permalink

What's the problem with CDR logging? what is not compatible on thirdlane dialplan? and which dialplan is fully compatible?

Submitted by eeman on Sat, 01/31/2009 Permalink

asterisk logs based on source and destination numbers. a lot of PBX dialplans will fork a call generating 2 or 3 entries in CDR, or they re-write the destinations to extensions like 's' or the handset extension. How are you going to bill incomming toll-free if your destination keeps showing up as 212 in the CDR because that is where they pointed the destination to.

The CDR you bill with needs to be clean and absolute, 1 CDR entry per call, with a clear source and destination TN. Don't fork calls with a second Dial statement, dont use chan_local. Stick with Goto's and/or Gosub's.