Scott Lawrence wrote: > On Thu, 2009-02-12 at 13:05 +0530, Chaitra wrote: >> Hi, >> Currently the 'Extension' field on the Conference, ACD line and Hunt >> group screens does not support numbers/extensions having prefix as + >> thus displaying an error message "Please enter digits only, for example: >> 123" >> >> Support for this would help in the following usecase: >> If a PSTN caller wants to join a conference by calling through ITSP, he >> has to dial the ITSP directory number, which in turn has to be assigned >> as the conference extension. To make this interoperable with different >> ITSPs, the conference extensions should support all types of number >> formats. This is true for other features such as ACD and Hunt Groups as >> well. >> >> The need for supporting extensions having prefix as + arises while using >> bandwidth.com as the ITSP. The Bandwidth numbers are in the default >> E.164 format, which is '+14444444444' . Hence it is mandatory that the >> SCS extensions have a prefix of +1 to receive the Inbound calls.
It's easier to maintain a dial rule that converts incoming numbers (for example by stripping +1 prefix) than to maintain aliases or extensions that match incoming numbers. >> >> Could this be implemented? If yes I would file an improvement/bug for >> the same. > > I agree - the + should be allowed as the first character anywhere a > phone number is expected. > > I think the idea was that extension is what you can type on the standard phone keyboard (it's defined as validPhone: [\d*]+). But I think it's completely arbitrary. Probably no reason not to allow for '+'. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
