- Community Home
- >
- Networking
- >
- Legacy
- >
- IP Telephony - NBX
- >
- Re: 3com NBX V3000- Invalid extension
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2011 01:51 AM - edited тАО05-11-2011 01:54 AM
тАО05-11-2011 01:51 AM - edited тАО05-11-2011 01:54 AM
3com NBX V3000- Invalid extension
I have 3com NBX V3000 system. Every time when external users try to reach direct extensions NBX plays the voice message тАЬINVALID EXTENSIONтАЭ, more than 80% of external users experiencing the same issue. They can not reach to direct extension but they able reach to reception that is тАШ0тАЩ Extension.
Product Details:
3com NBX V3000
Part number: 3C10600A - NBX V3000 System Analog
Current Software Version: R6_0_63
No. of Extensions: 30
No. of Analog Lines: 10
Kindly help me to solve this issueтАжтАж
--Kiran
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2011 08:41 AM
тАО05-11-2011 08:41 AM
Re: 3com NBX V3000- Invalid extension
Can you give more details?
How is the call coming in? is it via PRI card or BRI or Analog line?
When call arrives ,do they go to an Auto Attendant, then dial the extension? is this when they are getting the "invalid extension"?
This could be dtmf issue through the PRI/BRI or ALC....
Are you running in SIP mode?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2011 09:28 PM
тАО05-11-2011 09:28 PM
Re: 3com NBX V3000- Invalid extension
The call coming via Analog Line.
Yes, after call arrives they go to an auto attendant and it plays voice message which we recorded for announcement.
After hearing the voice the user trying to dial direct extension Number but instead of transferring the extension the NBX plays the voice message "INVALID EXTENSION". If the user dials "0" it transfers to our Reception which has extension 100.
Please find the attached Dial Plan of our NBX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2011 08:07 AM
тАО05-12-2011 08:07 AM
Re: 3com NBX V3000- Invalid extension
Go to the AA that you are using (NBX Messaging/Auto Attendant), click on the AA, then click on menu tree. Make sure that the beginning number is marked "reserved in dialplan", for example, if they are dialing x2345, make sure the 2 has "reserved in dialplan). I cannot see your dialplan, but in the case above, make sure that Table 2 has 2 in it also. If this is all set up correctly, then the issue is that the Ananlog line card is not recognizing the DTMF tones correctly. This could be an NBX issue or telco issue... What country pack are you using? Only way to get to the bottom of this, open a case with HP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2011 05:26 AM
тАО05-15-2011 05:26 AM
Re: 3com NBX V3000- Invalid extension
Hi Dear,
AA settings are fine. I am using United Arabic Emirates country pack. Please find the attached log file. You may find some more information in that. Kindly assist me to solve this issue.
Regards..
Kiran
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2011 05:00 AM
тАО05-16-2011 05:00 AM
Re: 3com NBX V3000- Invalid extension
I don't see log file attached.. can you cut and past what you deem relevant?
also, can you put in your dialplan?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2011 08:26 AM
тАО05-16-2011 08:26 AM
Re: 3com NBX V3000- Invalid extension
Check Table 2 devices using and make sure all of the correct devices are in there , also check your dial plan under table 2 and make sure the digit for the extension , example ext. 300 should have an entry for digit 3 pointed to route zero . Invalid extension means the NBx does not know what you are dialing .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2011 09:31 PM
тАО05-16-2011 09:31 PM
Re: 3com NBX V3000- Invalid extension
Dial Plan: 1st Part
/////////////////////////////////////////////////////////////////////////////////
/
/ NBX Dial Plan Configuration File
/ Generated from machine V3000 192.168.**.*** owned by Valued Customer 0
/ Generated on TUE MAY 17 08:22:40 2011
/
/////////////////////////////////////////////////////////////////////////////////
/ First, delete all existing dialplan information
Table Delete *
DestinationRoute Delete *
TimedRoute Delete *
PreTranslator Delete *
/ Now, create all dialplan information
/////////////////////////////////////////////////////////////////////////////////
/ Settings. Note: ACD ranges included in HuntGroup category.
/////////////////////////////////////////////////////////////////////////////////
ExtensionLength 3
ExtensionRange Telephone 100 399
ExtensionRange Park 600 619
ExtensionRange AutoAttendant 500 599
ExtensionRange HuntGroup 400 499
ExtensionRange External 600 799
/////////////////////////////////////////////////////////////////////////////////
/ The ExtensionRange External Setting MUST include the Park range.
/ If the Call Park range is outside of the ExtensionRange External,
/ the Call Park feature will not work.
/////////////////////////////////////////////////////////////////////////////////
ExternalSettings 9 750 500
/////////////////////////////////////////////////////////////////////////////////
/ Dial Plan Tables
/////////////////////////////////////////////////////////////////////////////////
Table Create 1 Internal 3 Digit Extensions
/ Id Entry Digits Min Max Class Prio Route
/ -- ----- ------------ --- --- ------------- ---- -----
TableEntry Create 1 1 1 3 3 Internal 0 0
TableEntry Create 1 2 2 3 3 Internal 0 0
TableEntry Create 1 3 3 3 3 Internal 0 0
TableEntry Create 1 4 4 3 3 Internal 0 0
TableEntry Create 1 5 5 3 3 Internal 0 3
TableEntry Create 1 7 6 3 3 Internal 0 0
TableEntry Create 1 8 7 3 3 Diagnostics 0 0
TableEntry Create 1 9 0 1 1 Internal 0 4
TableEntry Create 1 10 9 8 8 Local 0 1
TableEntry Create 1 11 900 4 32 International 0 1
TableEntry Create 1 12 902 10 10 LongDistance 0 1
TableEntry Create 1 13 903 10 10 LongDistance 0 1
TableEntry Create 1 14 904 10 10 LongDistance 0 1
TableEntry Create 1 15 9050 11 11 Wireless 0 1
TableEntry Create 1 16 906 10 10 LongDistance 0 1
TableEntry Create 1 17 907 10 10 LongDistance 0 1
TableEntry Create 1 18 909 10 10 LongDistance 0 1
TableEntry Create 1 19 91 4 4 Operator 0 1
TableEntry Create 1 20 9400 8 8 TollFree 0 1
TableEntry Create 1 21 9500 8 8 Other 0 1
TableEntry Create 1 22 9800 8 8 TollFree 0 1
TableEntry Create 1 23 9181 1 4 TollFree 0 1
TableEntry Create 1 30 997 3 3 Emergency 0 2
TableEntry Create 1 31 998 3 3 Emergency 0 2
TableEntry Create 1 32 999 3 4 Emergency 0 2
TableEntry Create 1 33 9997 4 4 Emergency 0 1
TableEntry Create 1 34 9998 4 4 Emergency 0 1
TableEntry Create 1 35 9999 4 4 Emergency 0 1
TableEntry Create 1 50 8 4 30 WAN 0 5
TableEntry Create 1 25 9055 11 11 Wireless 0 1
TableEntry Create 1 26 9056 11 11 Wireless 0 1
Table Create 2 Incoming 3 Digit DDI
/ Id Entry Digits Min Max Class Prio Route
/ -- ----- ------------ --- --- ------------- ---- -----
TableEntry Create 2 1 1 3 3 Internal 0 0
TableEntry Create 2 2 2 3 3 Internal 0 0
TableEntry Create 2 3 3 3 3 Internal 0 0
TableEntry Create 2 4 4 3 3 Internal 0 0
TableEntry Create 2 5 5 3 3 Internal 0 3
Table Create 3 Least Cost Routing
/////////////////////////////////////////////////////////////////////////////////
/ Routes
/////////////////////////////////////////////////////////////////////////////////
/ Route Description
/ ----- -----------
DestinationRoute Create 1 LocalCO
DestinationRoute Create 2 LocalCONoStrip
DestinationRoute Create 3 Voice Application
DestinationRoute Create 4 Attendant
DestinationRoute Create 5 H323 ConneXtions Ports
/ Route Entry DestinationExtension
/ ----- ----- --------------------
DestinationRouteEntry Create 1 1 *0001
DestinationRouteEntry Create 1 2 *0002
DestinationRouteEntry Create 2 1 *0001
DestinationRouteEntry Create 2 2 *0002
DestinationRouteEntry Create 3 1 *0003
DestinationRouteEntry Create 4 1 *0004
DestinationRouteEntry Create 5 1 *0005
/ Route Entry OperId Operation Value
/ ----- ----- ------ --------- -----
DestinationRouteOperation Create 1 1 1 stripLead 1
DestinationRouteOperation Create 1 2 1 stripLead 1
DestinationRouteOperation Create 5 1 1 stripLead 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2011 09:32 PM
тАО05-16-2011 09:32 PM
Re: 3com NBX V3000- Invalid extension
Dial Plan: 2nd Part
/////////////////////////////////////////////////////////////////////////////////
/ Pretranslators
/////////////////////////////////////////////////////////////////////////////////
PreTranslator Create 1 4Digit DDI 3Digit Internal
/ PreTransId Entry Digits
/ ---------- ----- ------
PreTranslatorEntry Create 1 1 1
PreTranslatorEntry Create 1 2 2
PreTranslatorEntry Create 1 3 3
PreTranslatorEntry Create 1 4 4
PreTranslatorEntry Create 1 5 5
PreTranslatorEntry Create 1 6 6
PreTranslatorEntry Create 1 7 7
PreTranslatorEntry Create 1 8 8
PreTranslatorEntry Create 1 9 9
PreTranslatorEntry Create 1 10 0
/ PreTransId Entry OperId Operation Value
/ ---------- ----- ------ --------- -----
PreTranslatorOperation Create 1 1 1 stripLead 1
PreTranslatorOperation Create 1 2 1 stripLead 1
PreTranslatorOperation Create 1 3 1 stripLead 1
PreTranslatorOperation Create 1 4 1 stripLead 1
PreTranslatorOperation Create 1 5 1 stripLead 1
PreTranslatorOperation Create 1 6 1 stripLead 1
PreTranslatorOperation Create 1 7 1 stripLead 1
PreTranslatorOperation Create 1 8 1 stripLead 1
PreTranslatorOperation Create 1 9 1 stripLead 1
PreTranslatorOperation Create 1 10 1 stripLead 1
/ End of configuration
/////////////////////////////////////////////////////////////////////////////////
/ Configuration file command syntax guide:
/ Table Create {nTableId} {szDescription}
/ Table Delete {nTableId}
/ TableEntry Create {nTableId} {nEntryId} {szDigits}
/ {nMinDigits} {nMaxDigits} {szCallClass}
/ {nPriority} {nRouteId}
/ TableEntry Delete {nTableId} {nEntryId}
/ DestinationRoute Create {nRouteId} {szDescription}
/ DestinationRoute Delete {nRouteId}
/ DestinationRouteEntry Create {nRouteId} {nEntryId} {szExtension}
/ DestinationRouteEntry Delete {nRouteId} {nEntryId}
/ DestinationRouteOperation Create {nRouteId} {nEntryId} {nOperId}
/ {szOperation} {szValue}
/ DestinationRouteOperation Delete {nRouteId} {nEntryId} {nOperId}
/ TimedRoute Create {nRouteId} {nDefaultDestinationRouteId} {szDescription}
/ TimedRoute Delete {nRouteId}
/ TimedRouteEntry Create {nRouteId} {nEntryId} {szStartTime} {szEndTime}
/ {szDaysOfWeek} {nDestinationRouteId}
/ TimedRouteEntry Delete {nRouteId} {nEntryId}
/ TimedRouteOperation Create {nRouteId} {nEntryId} {nOperId}
/ {szOperation} {szValue}
/ TimedRouteOperation Delete {nRouteId} {nEntryId} {nOperId}
/ PreTranslator Create {nPreTranslatorId} {szDescription}
/ PreTranslator Delete {nPreTranslatorId}
/ PreTranslatorEntry Create {nPreTranslatorId} {nEntryId} {szDigits}
/ PreTranslatorEntry Delete {nPreTranslatorId} {nEntryId}
/ PreTranslatorOperation Create {nPreTranslatorId} {nEntryId} {nOperId}
/ {szOperation} {szValue}
/ PreTranslatorOperation Delete {nPreTranslatorId} {nEntryId} {nOperId}
/ PreTranslatorISDNNumberType {nPreTranslatorId} {nISDNNumberType}
/ ExtensionLength {nExtensionLength}
/ ExtensionRange {szExtensionType} {szLowestExtension} {szHighestExtension}
/ ExternalSettings {szExternalKeysetPrefix} {szFirstAutoDiscoverExtension}
/ {szDefaultAutoExtension}
/ Notes: 1. Each command must be entered on one line.
/ 2. Commands are case insensitive.
/ 3. Tabs and spaces are ignored except in szDescription arguments.
/ 4. The {} shown enclosing command argument names should not
/ be included in commands.
/ 5. Command arguments beginning with n must be numbers.
/ 6. Command arguments beginning with sz are strings.
/ 7. nTableId 1 is the default Internal 3 digit dial plan table.
/ 8. nTableId 2 is the default Incoming 3 digit dial plan table.
/ 9. nTableId 3 is the default LCR dial plan table. (If used the
/ LCR table is checked first, if no entry exists, string is then
/ run through the associated internal dial plan.
/ 10. szExtension *0001 is the default Line Card Port extension list
/ 11. szExtension *0002 is the default T1 extension list
/ 12. szExtension *0003 is the default Voicemail extension list
/ 13. szExtension *0004 is the default Attendant extension list
/ (The lowest telephone extension that is Auto-discovered will
/ populate)
/ 14. szExtension *0005 is the default H323 extension list
/ 15. szExtension *0008 is the default 8 Pool extension list
/ (for backward compatibility, 8 Pool from R1.x upgrades)
/ 16. szOperation can be: stripLead stripTrail replace prepend append
/ 17. szCallClass can be: Internal Local LongDistance International WAN
/ TollFree Emergency COCode Other Wireless Toll
/ AlternateLong Operator TrunkToTrunk Diagnostics
/ NotAllowed
/ 18. route 0 always means look up internal device by extension
/ 19. szStartTime and szEndTime are military time 00:00 through 23:59
/ 20. szStartTime and szEndTime can be: open closed lunch other
/ (if specifying a system mode, both must be the same mode)
/ 21. szExtensionType can be: telephone, park, autoAttendant, huntGroup,
/ external, page
/ 22. nISDNNumberType types for ETSI are as follows: (0, default) unknown;
/ (1) international; (2) national; (3) network; (4) subscriber
/////////////////////////////////////////////////////////////////////////////////
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2011 06:35 AM
тАО05-17-2011 06:35 AM
Re: 3com NBX V3000- Invalid extension
hi.
You never stated what extension your customers are dialing when they get "invalid extension".
INcoming calls and Auto Attendant calls hit Table 2... in Table 2, you have no entries for numbers beginning with 6,7,8, or 9.. That would yield an "invalid extension"... Just copy the entries from TAble 1 and input into table 2.
Of course, if you are dialing any number beginning with 1,2,3,or 4, something else is going on.
The best way to see if this is a config or dialplan issue is to dial your AA from an internal phone, then dial the extension.. do you get an "invalid extension". If you do, it is a dialplan or config issue.
If you do not and the call goes through, then it could be the analog line card is not recognizing the dtmf digits.