Alcatel Unleashed

When using Mincom and the voicemail V24 is connected on ttyS2 or ttyS3 if the 4400 system is reset the voicemail system never comes back into service.
Have tries various V24 port setting but no luck.

Regards
Rlong

Never seen this. Post your minicom configuration.

Hi, I have just setup the minicom connection on a site as their RAMB card failed and they don't want to repair it. I have configured as per the doc on this website and the port used is ttyS3. I have the same issue as Rlong. the other night I loaded new OPS files and rebooted. the VPU5 would not come back. I tried a few VPU reboots but they only way it will come back is by unplugging the console cable from Port "D" then when the VPU is up I can reconnect it and use minicom to manage. I could see the VPU halts not long after it rebuilds NMT tables.

Any ideas?

I See this issue consistantly in lab testing. tot3nkopf the minicom config is below. If cable is unplugged from D then problem does not occur. When rebooting the Vmail reports a bell test problem (I don't have the exact issue text to hand but I will post it shortly)

A - Serial Device : /dev/ttyS3 (this is port D on connection box )
B - Lockfile Location : /var/lock
C - Callin Program :
D - Callout Program :
E - Bps/Par/Bits : 9600 8N1
F - Hardware Flow Control : No
G - Software Flow Control : No

A - Init string ......... ^M
B - Reset string ........ ^M~ATZ^M~
C - Dialing prefi #1.... ATDT
D - Dialing suffi #1.... ^M
E - Dialing prefix #2.... ATDP
F - Dialing suffix #2.... ^M
G - Dialing prefix #3.... AT 1DT
H - Dialing suffix #3.... ; 4D^M
I - Connect string ...... CONNECT
J - No connect strings .. NO CARRIER BUSY
NO DIALTONE VOICE
K - Hang-up string ...... ~~+++~~ATH^M
L - Dial cancel string .. ^M

M - Dial time ........... 45 Q - Auto bps detect ..... No
N - Delay before redial . 2 R - Modem has DCD line .. Yes
O - Number of tries ..... 10 S - Status line shows ... DTE speed
P - DTR drop time (0=no). 1 T - Multi-line untag .... No

Change which setting? (Return or Esc to exit)

# chmod 777 /usr/bin/minicom
#chmod 777 /var/lock
#chmod 777 /dev/ttyS3

Remove the init and reset strings, save and try again.
Also, be sure that the port is configured as 4635 access in PBX (v24 config).

Regards.

I will try this tomorrow and update. FYI the error on the start up of 4635 is this

Please stand by while rebooting the system...
Restarting system.

*** BIOS Version 3BA_24095_AAAB_07 ***
*** Generated on fillld0f00258 on Nov/09/2006 at 15:15 ***
*** CPU6 Step 2 version 3BA 23197 : 0.1 ***
*** ELAN SC520 @ 100MHz ***

.. Abnormal BEL char received on TTY # TTY0
.........

Hi, on my site the init and reset strings are blank and the voicemail goes further into the startup. It fails later on but I can't trace it as the site is remote and I don't get there very often.

Hi All,

Tested with the init & reset still didn't come up. Next test is to remove all mincom config (as if never configured) and just see what happens with cable connected to D...

so not a minicom issue at all. Fresh install no minicom config and just cable connected to D port and issue re-occurs...e-SR methinks