Hello,
I want to create the S 'Default when no DID' route for my tenants on PBX Manager MTE.
How do I go about doing this?
I just want to setup a default route when there is no DID. When I go to create route it always asks for a DID so I can't do this.
How do I create an invalid handler for my tenants?
Regards
Brian
Thanks Erik, I understand. I
Thanks Erik,
I understand.
I am doing a number port for a customer next week. There will be 200 DID's coming to us.
They will be checked by the telco for 1 ring while the port is happening and if this doesn't happen the numbers will revert to the donor telco.
They are all setup on our proxy and pointing at a trunk on MTE.
I can setup the DID range easily in MTE. How would i get all these DID's to ring one extension without having to setup a route for each. I was thinking an invalid handler but obviously I was incorrect.
Any suggestions?
Thanks
Brian
You say you have a proxy...
You say you have a proxy... why not set up a VERY basic asterisk box to deal with this.. lets say that box has something like
sip.conf
[proxy]
type=peer
host=ip.addr.of.proxy
insecure=port,invite
context=from-outside
disallow=all
allow=g711
extensions.conf
[from-outside]
exten => _X.,1,Goto(sample-ivr,s,1)
exten => _+X.,1,Goto(sample-ivr,s,1)
exten => s,1,Goto(sample-ivr,s,1)
exten => i,1,Goto(sample-ivr,s,1)
[sample-ivr]
exten => s,1,Ringing
exten => s,n,Wait(10)
exten => s,n,Answer
exten => s,n,Playback(spam)
exten => s,n,Hangup
once you own the number, then update your proxy to go back to MTE. This box doesn't have to be anything significant, even a virtual machine could achieve this task.
200 dids for a single tenant
200 dids for a single tenant seems crazy. Im surprised you didnt try to sell them single-tenant edition and let them have their own pbx. Seems that with that many DIDs comes that many handsets, concurrent calls, and possibly a lot of special requests.
that's what I love about Thirdlane. There is an MTE solution, and if they outgrow that, or have special needs, there's an STE version also. The interfaces are identical which makes training, support, and upkeep a breeze.
I agree. They will not be
I agree.
They will not be using them. To port their main 2 numbers the provider was failing the port if we didn't take the DID range also.
So to get their main 2 numbers we need to port the entire range from their PRA.
Then the caveat is if any of the numbers don't ring active during the port the port fails.. A real pain in the ass but this is the way this incumbent operates.
I am going to do something permanent along the lines of what you suggested re proxy and dedicated box to just ring for these cases.
Thanks for your help
brian
you cant. I dont think you understand how this works. 's' is an extension just like anything else. You are literally saying.. i want all my tenants to each have an inbound route for 5555551212 .. only one tenant can be assigned a specific extension in the inbound route section. Its in that context that determines who the tenant is, not the other way around. Also 's' is not an invalid handler, 's' is an extension used when the extension field is missing (example: analog lines ALWAYS process against 's' because there is no DNIS signaling on analog).
The only reason there is an 's' at all in MTE is to deal with some switches in Europe that do not send proper SIP INVITE messages indicating who the call is for. Instead they put the DNIS in an add-on header they used called 'To'. So the 's' extension in MTE can be used to process a script that parses the 'To' header from the SIP INVITE message and then executes a GoTo on that header. There should be no other reason in MTE that calls are processing against 's'.