hosted Posted December 5, 2008 Report Share Posted December 5, 2008 ok i am not good at trunk routing, can someone help me? I have an inbound trunk and I want to pass 80122233xx to trunk OCS and 80122244xx to trunk Exchange directly. and everything else can be processed in the domain. how would i write that? Quote Link to comment Share on other sites More sharing options...
hosted Posted December 6, 2008 Author Report Share Posted December 6, 2008 is this possible to do? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 7, 2008 Report Share Posted December 7, 2008 ok i am not good at trunk routing, can someone help me? I have an inbound trunk and I want to pass 80122233xx to trunk OCS and 80122244xx to trunk Exchange directly. and everything else can be processed in the domain. how would i write that? I would do that with the static registration. See http://wiki.pbxnsip.com/index.php/Extension#Registrations. Otherwise you will have trouble with the "charge for redirect" setting in the trunk. The limitation is that you need an extension account for every redirection that you want to program. Quote Link to comment Share on other sites More sharing options...
hosted Posted December 7, 2008 Author Report Share Posted December 7, 2008 yea thats what i was trying to avoid plus i need to redirect a block of 100 DID's. so basically i just need a UDP to TCP converter. maybe i should just use SIPx Quote Link to comment Share on other sites More sharing options...
Nikolay Kondratyev Posted December 8, 2008 Report Share Posted December 8, 2008 i'm new to pbxnsip but... could it be done using "Assume that call comes from user" setting on the inbound trunk and thats user personal dialplan? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 8, 2008 Report Share Posted December 8, 2008 yea thats what i was trying to avoid plus i need to redirect a block of 100 DID's. so basically i just need a UDP to TCP converter. maybe i should just use SIPx the PBX is a bad protocol converter.... Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 8, 2008 Report Share Posted December 8, 2008 i'm new to pbxnsip but...could it be done using "Assume that call comes from user" setting on the inbound trunk and thats user personal dialplan? The problem with that setting is that it applies to all incoming numbers then and not only to a range... Quote Link to comment Share on other sites More sharing options...
Nikolay Kondratyev Posted December 8, 2008 Report Share Posted December 8, 2008 The problem with that setting is that it applies to all incoming numbers then and not only to a range... My idea was: one can create a special fake user, and a special dialplan, which is to be used for incoming call analysis. So one will be able to use several regular expressions to route incoming calls... Each range may be routed via it's own dialplan entry... In particular, this alows transit routing.. Is it bad idea? (Why?) Rgds, Nikolay. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 8, 2008 Report Share Posted December 8, 2008 My idea was: one can create a special fake user, and a special dialplan, which is to be used for incoming call analysis.So one will be able to use several regular expressions to route incoming calls... Each range may be routed via it's own dialplan entry... In particular, this alows transit routing.. Is it bad idea? (Why?) Oh so you mean routing everything through one extension? Might be tricky, but could actually work... I guess you have to tell the domain to keep the From/To headers unchanged. Then in the trunk you could just use a pattern like "!123456[0-9]{2}!123!t!" that would send all calls to 123456xx to extension 123, then there you can use a static registration with something like "<sip:exchange@192.168.1.2;transport=tcp>". I did not try this, bug it might get "closer". Quote Link to comment Share on other sites More sharing options...
Nikolay Kondratyev Posted December 8, 2008 Report Share Posted December 8, 2008 Oh so you mean routing everything through one extension? Might be tricky, but could actually work... I guess you have to tell the domain to keep the From/To headers unchanged. Then in the trunk you could just use a pattern like "!123456[0-9]{2}!123!t!" that would send all calls to 123456xx to extension 123, then there you can use a static registration with something like "<sip:exchange@192.168.1.2;transport=tcp>". I did not try this, bug it might get "closer". I would say in another way: i mean using dial plan for incoming call routing. Not just single regular expression in the "send call to extention" field. The wiki page ( http://wiki.pbxnsip.com/index.php/Trunk_Settings ) says: The setting "Assume that call comes from user" is used for trunks that accept redirects (see above). The settings must be an extension in the domain of the trunk. This setting is necessary in order to determine what dial plan to use; and it is also necessary to charge a user on the system for the call. For regular trunks, you should leave this field empty. So, i make a conclusion that one can route incoming calls through a dialplan, where further flexible routing to different sip trunks (or flexible DID mapping) can be achieved. Of course From/To header must be preserved in this case. If all calls are routed through one extention, then - ok, since From/To headers are the same. And as far as i can see in log, the field "Send call to extension" is just ignored in this case. I tried to do this and i was able to route a call to pbxnsip extension and to another trunk..., though i found some problems... So the question is: is it a proper way to route incoming calls? Thanks in advance, Nikolay. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 8, 2008 Report Share Posted December 8, 2008 So the question is: is it a proper way to route incoming calls? The handling of calls coming from a trunk were designed to send them to internal destinations. If we are starting to send them to external destinations we get into new areas. The problem occured for Microsoft Exchange and OCS; so we introduced some ad'ons to make this possible. But I would not call that a "proper way" to route incoming calls. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.