- 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
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
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-17-2011 10:09 PM
05-17-2011 10:09 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2011 06:58 AM
05-18-2011 06:58 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2011 07:52 AM
05-18-2011 07:52 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2011 10:30 PM
05-18-2011 10:30 PM
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=
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2011 05:47 AM
05-19-2011 05:47 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2011 10:46 AM - edited 05-24-2011 10:47 AM
05-24-2011 10:46 AM - edited 05-24-2011 10:47 AM
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 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2011 12:47 AM
05-25-2011 12:47 AM
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=
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2011 12:48 AM - edited 05-25-2011 12:50 AM
05-25-2011 12:48 AM - edited 05-25-2011 12:50 AM
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=
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2011 12:49 AM
05-25-2011 12:49 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2011 06:37 AM
05-26-2011 06:37 AM
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