How the legacy PBX is supposed to reach the users moved onto sipX? > Though the PSTN How the calls from the legacy PBX will hit the sipX box? > In from the PSTN though our SIP trunk provider
If all the moved users have DID numbers, you just need to add an alias for each one. If not, maybe setup an auto-attendant on the sipX asking for the extension number. Yes the alias answer seem ok for scenario 1) Thanks On Wed, May 20, 2009 at 10:24 AM, Melcon Moraes <mel...@gmail.com> wrote: > How the legacy PBX is supposed to reach the users moved onto sipX? > How the calls from the legacy PBX will hit the sipX box? > > If all the moved users have DID numbers, you just need to add an alias for > each one. If not, maybe setup an auto-attendant on the sipX asking for the > extension number. > > - > MM > > > On Tue, May 19, 2009 at 7:08 PM, Hazza <hazz...@gmail.com> wrote: > >> Basically I need three things: >> 1) We have a legacy pbx. During migration I want people that are moved >> onto sipx to still be able to dial 4 digit extentions for people on the >> legacy pbx. So they should be able to dial a 4 digit extension and sipx will >> map this to an external number i.e. 6600->041234567 >> >> 2) I would like to do the reverse of the above. So when people on the >> legacy pbx dial the people on the sipx system the incoming caller-id on sipx >> is mapped to the extension number from above. 41234567->6600 >> >> 3) Our sip trunk provider provides incoming caller-id with out the long >> distance (0) or international (00) prefix. I would like to put these on to >> the incoming caller-id i.e. 8 digit national number 41234567 to 041234567. >> This is related to 2) as well. >> >> I can see that I can do 1) with "phantom" extensions as suggest by Michael >> - hopefully through the csv loader. Can I do anything about 2) and 3)? We >> have piloted asterisk and did to above with custom context/dialplans. >> >> Thanks for your patience >> >> On Wed, May 20, 2009 at 9:41 AM, Scott Lawrence < >> scott.lawre...@nortel.com> wrote: >> >>> On Wed, 2009-05-20 at 09:18 +1200, Hazza wrote: >>> > The .com missing is a sanitising problem. I don't seem to be able to >>> > make this work (or don't really understand it. Is the domain my domain >>> > or the trunk providers domain? I have tried both with no luck. >>> >>> back up and describe your configuration, what you expect, and what >>> really happens, but do it on the list >>> >>> >>> >> >> _______________________________________________ >> 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 >> > >
_______________________________________________ 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
