IP Telephony - NBX
cancel
Showing results for 
Search instead for 
Did you mean: 

3com NBX V3000- Invalid extension

NIHC
Occasional Advisor

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

20 REPLIES
bosoxfan
Trusted Contributor

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?

NIHC
Occasional Advisor

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

bosoxfan
Trusted Contributor

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.

NIHC
Occasional Advisor

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

bosoxfan
Trusted Contributor

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?

 

merlin215
Valued Contributor

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 .

NIHC
Occasional Advisor

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


NIHC
Occasional Advisor

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
/////////////////////////////////////////////////////////////////////////////////

bosoxfan
Trusted Contributor

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.

NIHC
Occasional Advisor

Re: 3com NBX V3000- Invalid extension

Extension Series starts with 100, total no. of users: 33

 

 

 

I have dialed all the extensions through AA, all of them responding correctly.

bosoxfan
Trusted Contributor

Re: 3com NBX V3000- Invalid extension

If you can dial all the extensions through the AA and they dial fine and the only issue is when you are coming

through the analog line card, then the issue is the dtmf in the analog line card.. either card not recognizing it or the telco is not sending a legitimate dtmf.

 

YOu could try going to PSTN Gateway Configuration/Analog line card/Advanced settings and increase the Audio Input gain.. the default is 3.... this will increase all audio.... there is a small chance this will help.

Unfortunately, the only way to resolve this is to open a case with HP.. this involves some very intricate troubleshooting.

bosoxfan
Trusted Contributor

Re: 3com NBX V3000- Invalid extension

here is something you can take a look at.

Make a call when you get an "invalid extension" number.

Then , in your URL, type in http"\\ip address of nbx\htfs0\NBossLog.txt (watch the upper and lower case)

 

look for  a ROUTER error, you should see something like "extension profile is null for extension=xxx.

I am sure it will not be the extension you typed in but something different... DO a few tests with different

extension numbers, maybe just one number is off... maybe you will see that instead of a "1", the dtmf is something differetn... Then I would get in touch with my telco and tell them...Let them check.

Only way for HP to check is for you to open a case, run what is called an RTCollect, which shows the modulation of the dtmf signal.

NIHC
Occasional Advisor

Re: 3com NBX V3000- Invalid extension

Please find the attached log file.

 

most of the errors hit to the extensions which are not existed in our network. And other errors shows as below.

 

Router         E Routing algorithm failed for inDigits=0 RouteId=4

 

Router         E [Routing by Device Profile]Device Profile is Null for Extension=    

 

 

bosoxfan
Trusted Contributor

Re: 3com NBX V3000- Invalid extension

I see the error "extension profile is null for extension = "

but is there any extension there?

It is now quite clear that the analog line card is not recognizing the dtmf digits being sent. This is

either because:

1. the dtmf digits being sent are not within the spec

or

2. the dtmf digits are within the spec but analog line card not recognizing them.

 

Like I said, you could contact your telco and ask them to do a test... you need to contact HP and open up a case.

This now involves getting something called an "RTCollect" and having HP network engineers review to ensure that the dtmf are within spec (or a bug on the alc card with the UAE country pack)

 

another thing you might try, go to country settings/Advanced regional settings, change the tones and cadences to United states. .. this requires a reboot of the NBX.. this will prove if issue is with the UAE country pack or alc , if not with telco... however, you may have some issues with the analog line card call being disconnected so you should just do this as a test and then change it back.

merlin215
Valued Contributor

Re: 3com NBX V3000- Invalid extension

If you send the call to a tel  say a reception tel or somes telephone , then press the digits , do they sound ok ? 

I have to guess that these are standard telco lines and not a digital line and turning them into an analog line ?

Are the direct from your telco ? 

NIHC
Occasional Advisor

Re: 3com NBX V3000- Invalid extension

PART-1

 

Please find the following logs, monitored on different settings.

 

  • When selected country and language = United states:

 

0524:112103:0769 Router         W All Voice Mail ports on route are busy                                                                                 
0524:112103:0788 Router         E Routing algorithm failed for inDigits=500FAAAAA4#126#6777500*F RouteId=3                                               
0524:112115:0942 Router         W All Voice Mail ports on route are busy                                                                                 
0524:112115:0942 Router         E Routing algorithm failed for inDigits=500FAAAAA4#124#6777500*F RouteId=3                                               
0524:112128:0326 Router         W All Voice Mail ports on route are busy                                                                                 
0524:112128:0346 Router         E Routing algorithm failed for inDigits=500FAAAAA4#110#6777500*F RouteId=3

 

 

  • country and language = United Arab Emirates

 

Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0524:112951:0634 Router         W All Voice Mail ports on route are busy                                                                                 
0524:112951:0634 Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0524:113000:0692 Router         W All Voice Mail ports on route are busy                                                                                 
0524:113000:0692 Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0524:113005:0634 Router         W All Voice Mail ports on route are busy                                                                                 
0524:113005:0634 Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0524:113007:0134 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0524:113015:0634 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0524:113020:0403 Router         W All Voice Mail ports on route are busy                                                                                 
0524:113020:0403 Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0524:113024:0730 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0524:113031:0153 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0524:113039:0653 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0524:113044:0423 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0524:113048:0749 Router         E [Routing by Device Profile]Device Profile is Null for Extension=  

NIHC
Occasional Advisor

Re: 3com NBX V3000- Invalid extension

PART-2

  • country and language = United Arab Emirates and Advance Regional Settings>Tones and Cadences:USA

Router         W All Voice Mail ports on route are busy                                                                                 
0525:093649:0038 Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0525:093702:0192 Router         W All Voice Mail ports on route are busy                                                                                 
0525:093702:0192 Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0525:093708:0653 Router         W All Voice Mail ports on route are busy                                                                                 
0525:093708:0653 Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0525:093713:0057 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093715:0134 Router         W All Voice Mail ports on route are busy                                                                                 
0525:093715:0153 Router         E Routing algorithm failed for inDigits=500FAAAAA4#113#0506425223*F RouteId=3                                            
0525:093726:0249 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093732:0653 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093737:0076 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093744:0269 VAILSess3      W Received bad Event WatchdogTimeout in State Transfer                                                                   
0525:093750:0269 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093755:0038 VAILSess0      W Received bad Event WatchdogTimeout in State Transfer                                                                   
0525:093756:0673 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093801:0096 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093808:0615 Router         E Routing algorithm failed for inDigits=90501243162 RouteId=1                                                            
0525:093813:0384 Router         E Routing algorithm failed for inDigits=90506694433 RouteId=1                                                            
0525:093814:0288 Router         E Routing algorithm failed for inDigits=90501243162 RouteId=1                                                            
0525:093814:0307 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093814:0653 VAILSess1      W Received bad Event WatchdogTimeout in State Transfer                                                                   
0525:093820:0096 Router         E Routing algorithm failed for inDigits=90506694433 RouteId=1                                                            
0525:093820:0692 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093821:0192 VAILSess2      W Received bad Event WatchdogTimeout in State Transfer                                                                   
0525:093825:0115 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093838:0326 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093844:0711 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093849:0134 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093902:0346 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093902:0461 Router         E Routing algorithm failed for inDigits=90508198277 RouteId=1                                                            
0525:093908:0730 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093913:0153 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:093935:0538 Router         E Routing algorithm failed for inDigits=90558035917 RouteId=1                                                            
0525:093940:0942 Router         E Routing algorithm failed for inDigits=90558035917 RouteId=1                                                            
0525:093959:0961 DBI            W No Personal Operator configured for user at extension: [113]                                                           
0525:094015:0230 Router         E Routing algorithm failed for inDigits=90558232513 RouteId=1                                                            
0525:094022:0288 Router         W All Voice Mail ports on route are busy                                                                                 
0525:094022:0307 Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0525:094046:0326 Router         E [Routing by Device Profile]Device Profile is Null for Extension=

NIHC
Occasional Advisor

Re: 3com NBX V3000- Invalid extension

PART-3

  • Back to the same, country and language = United Arab Emirates

 

0525:104736:0826 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:104756:0115 Router         E Routing algorithm failed for inDigits=90567833476 RouteId=1                                                            
0525:104800:0846 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:104823:0249 Transfer       W 104 : OtherParty's extension= 113                                                                                      
0525:104824:0865 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:104851:0749 Router         W All Voice Mail ports on route are busy                                                                                 
0525:104851:0749 Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0525:104857:0538 Router         W All Voice Mail ports on route are busy                                                                                 
0525:104857:0538 Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0525:104909:0788 Router         W All Voice Mail ports on route are busy                                                                                 
0525:104909:0807 Router         E Routing algorithm failed for inDigits=500FAAAAA4#100#100*F RouteId=3                                                   
0525:104915:0788 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:104921:0576 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:104933:0807 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:104939:0615 VAILSess3      W Received bad Event WatchdogTimeout in State Transfer                                                                   
0525:104939:0807 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:104945:0596 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:104951:0923 VAILSess1      W Received bad Event WatchdogTimeout in State Transfer                                                                   
0525:104957:0826 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:104957:0884 VAILSess0      W Received bad Event WatchdogTimeout in State Transfer                                                                   
0525:105003:0826 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:105009:0615 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:105021:0846 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:105027:0846 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:105033:0634 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:105038:0461 Router         E Routing algorithm failed for inDigits=90501294182 RouteId=1                                                            
0525:105045:0865 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:105051:0461 Router         E Routing algorithm failed for inDigits=90501294182 RouteId=1                                                            
0525:105051:0865 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:105057:0653 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:105101:0134 Router         E Routing algorithm failed for inDigits=90501294182 RouteId=1                                                            
0525:105109:0884 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:105112:0115 Router         E Routing algorithm failed for inDigits=90501294182 RouteId=1                                                            
0525:105115:0884 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:105121:0673 Router         E [Routing by Device Profile]Device Profile is Null for Extension=                                                       
0525:105125:0326 Router         E Routing algorithm failed for inDigits=90501294182 RouteId=1   

 

 

While doing above process, I found some issues with NBX, when I use Regional Language: USA or Tones and Cadences: USA,

1. After reaching the call to a particular extension and if the extension does not answer it auto forward to reception extension -100. This may configuration issue as per country.

2. Even caller ends the call the extensions keep ringing for 8 to 10 rings more and auto forward to extension 100 (even there is not active incoming tone). It performs the same when I use Regional Language: UAE, but here after disconnect the call the number of rings up to 5 then disconnect.

bosoxfan
Trusted Contributor

Re: 3com NBX V3000- Invalid extension

Wow.. a couple of things

1. you do not have enough voicemail ports.. you should check. You should go to NBX Messaging/Configure/Port Usage and check how many times you ahve hit the max. number of vm ports.

2. the "routing" errors to 5000faaaaa4#extnumber.... are calls going to a persons voicemai.. probably related to item 1 above.

3. you have a routing error to 9050xxxxxx... check dialplan.. 9050xxxx goes to route 1, which is *0001, then

it stripleads 1 digit so sends out 050xxxx. .is this ok in your country

4. your original issue, call coming in, then hit dtmf not being recognized.. it is difficult to match that action with

an error here... can you match? run test and see what is new in the router log.. but there are a lot of calls not getting routed.

5. as for everything timing out going to x100.. you probably have that in your AA Menu tree.... timeout usually goes to the lowest extension number, which by default is the operators extension. You can change that by going to the AA/Menu tree

6. as for the disconnect, the US country pack uses a "Supervisory" disconnect.. UAE country pack uses a tone disconnect... so, with the US country pack your calls would not be disconnected because the telco is sending a tone disconnect.... this was for a test to see if the dtmf's would come through

nutrie
Advisor

Re: 3com NBX V3000- Invalid extension

I have run into this problem on many systems. It seems to be related to the way telcos are delivering analog lines from the CO.  I am guessing they are using SIP trunks to deliver the dial tone. If you look at the analog line card port and click Show DTMF digits you can see the digits that ALC recognizes. in a failure I see the 1st digit missing.

I have always assumed it's a telco issue using the logic it worked before... what changed? the telco...

Has 3com/HP found any solutions by making changes on the NBX to help resolve this issue..

Nick