IP 403 V2 Cutting Off Isdn as data calls hit system 1

[IPmonkey]

We use an ISDN Modem to remotely access our IP Office systems. A New 403 V2.0(16) with (BT) PRI 30 is loosing connection to the ISDN & Rebooting when a data call is presented to the IP Office. ANY IDEAS?

 

[MrIPO]

I am getting this on 90% of version 2 sites, when coming in over PRI or BRI to perform remote access via a ISDN modem.
Some site running version 2 are ok however.

1.4(25)(27) no problems. Has anybody been able to find what the issue is ???

The tracing from both 1.4(27) and Version 2.0(16) and 2.0(1602) look the same too me.

Any ideas ?

 

[IPGuru]

NO problems with remote access to any 2.0(16) sites here
however we did have this problem with a site runing 2.0(1602) on Bri lines
Downgrading to 2.0(16) resolved this issue

 

[Hesselvig]

Hi gazhall

We have the same problem with a 406 BRI Version 2.0(16). When a data call is presented to the IP Office the system Rebooting and in some cases we must disconnect the power from the system to get it running again.

This problem came first after we've reconfigured the system with the Wizard, so I think that the problem is the Wizard.

Did you configure your system with the wizard. ?

 

[IPmonkey]

Hesselvig The answer is yes. I don't normally use the wizard but in this instance I did. Thought id give it ago as thats what its there for.

 

[telepaul]

Hi

We had the same problem when upgrading from a ip 406 1.4(25) to 2.0(1602)
But after removing all the ras and remote users settings and a reboot of the system,
We reconfigured the settings for the remote user and ras, and we had no longer problems.

In to the monitor we had this error.

129735mS PRN: TFTPServer::RRQ(from 192.168.1.17) nasystem/licence_list
129819mS PRN: .FATAL TLB Data Error address=00000154 d=5 pc=016c2b3c 0164f2c8 016bf668 016bfee4 016b9bdc 016b91d8 IP 406 2.0(16)

********** contact lost with 192.168.1.61 at 08:42 19/1/2004 - reselect = 2 **********


I hoop this helps

 

[MrIPO]

Confirmed fix.
There is a problem with the Version 2 wizard, and a currupts database, in regard to RAS calls

The fix is
Under the Default Dialin RAS service
Add an extension number
Press OK
Do not save the config
Go in and remove the Extension number
Save configuration to switch.

This will rebuild this section of the database.

 

[smpatel1]

It the wizard that caused these problems - I had one unit that did this, I had to re-write the config to fix it.
Also I notice that there was problems with calling extentions on some occation - the user would dial 221 and it would call 224, no they did not have forwarding on.

re-write fixed this as well.

 

[raknas]

I have had this on a couple of occasions on new ip office installs using the admin wizard. I found if you remove the following

user= RemoteManager
ras= DialIn
iproute= RemoteManager
Incomingcall route= DialIn
reboot unit the add the above back again it fixes the problem.

 

[IPslug]

I have had the problem on a lot of my version 2 sites, it did turn out to be the wizard.Once the RAS,IP Route, and the user had been removed and added back in it all worked fine.