Ok. I am dredging this back up... sorry. In 4.2 I can do Internet dialing by default using the default sbc, sipXbridge-1. I do not have to enable Internet dialing by default to dial by sip URI.
What I do find is that ISN dialing, which used to be defined "allow ISN dialing" was located under Domain or Internet calling. Now it is under the registrar. Hurray it works! But, I am wondering "why" it is under registrar? I understand the base prefix might be under registrar... but I am also wondering if "enabling" it should not be under dial plans (simplify). On Wed, Oct 28, 2009 at 9:59 AM, Scott Lawrence <scott.lawre...@nortel.com> wrote: > On Wed, 2009-10-28 at 09:40 -0400, Tony Graziano wrote: >> I am testing some functionality with sipXbridge. I am curious if ISN >> dialing is supported via sipXbridge. >> >> What I think I know: >> >> Internet calling does not need to be enabled if using sipXbridge, it >> does it natively. >> sipXbridge does ITSP trunking >> sipXbridge supports remote workers (Nat traversal, via media relay) >> >> Since there is no dial plan for ISN, and you can natively enable it >> via registrar, what does one need in place to support ISN lookup and >> dialing. I assume it would be an independent SBC. >> >> Am I correct? > > Not quite. > >> Internet calling does not need to be enabled if using sipXbridge, it >> does it natively. > > The Internet Calling checkbox controls whether or not you can route to > an arbitrary SIP URL somewhere on the internet. Since that's what ISN > dialing provides a telephone-keypad way to do, you do need to enable > Internet Calling. > >> sipXbridge does ITSP trunking > > True, but it can also be used to route to unconfigured targets if you > enable Internet Calling. > >> sipXbridge supports remote workers (Nat traversal, via media relay) > > Nope - remote workers connect directly to the sipXproxy. The media > relay is shared between the bridge and the proxy. > > ISN dialing (see http://freenum.org/) provides a way for the registrar > to translate a dial string like 123*5678 into a sip url > 1...@some.example.org. The actual routing of the request is then done > using normal SIP rules. If you're not putting your sipXecs system > directly on the public Internet, then you need to route the call through > an SBC to allow the traffic in and out. You can use sipXbridge as that > SBC. > > > > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec. _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
