Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) Maxdial not dialling out on a 4000 with 6.1.3 & E1
Hi,
Just for the heck of it I decided to have a play with Maxdial and outgoing
calls. I've setup one of our MAX4000en with immediate modem on 5000, with a
password-protected global security setting (I've also tried "None").
Regardless of whether I telnet to the max on port 5000, or use MaxDial
under 95 (*shudder*) it won't dial out. It accepts the initialisation
string and command to dial, but sits there thinking for 60 seconds before
coming back with NO CARRIER.
Mdialsess shows:
entry slot:mdm route port hookDetect timr state
1 7:4 83 32 pollForOff n Await_Off_Hook
This changes to Await_digits while it pauses for 60 seconds.
The general status screen from the windowed console shows "Outdoing call
[number]", then "No connection", then "Call Terminated", all within the
space of ONE second. Oh, I've tried the +MS strings to set the correct
x-law without success (that was fixed before 6.1.3, right?)
What am I missing? %)
Cheers,
Kerrin
Revision: system revision: feik.m40 6.1.3
Here is some debug output:
(I do ATDT 82744888 here)
MODEMDRV-7/4: _hdlcBufRcvdFnc: data=6E125C28, len=1, parseState[n,v]=[0,0],
status= RCVD
MODEMDRV-7/4: data =
MODEMDRV-7/4: _processHookChgForVC:isOnHook=0
MODEMDRV-7/4: modemReOpenVC/ VIRTUAL_CNNCT
MODEMDRV-7/4: _processHookChgForVC:isOnHook=0
(sits here for around 60 seconds)
MODEMDRV-7/4: _processHookChgForVC:isOnHook=1
MODEMDRV-7/4: _hdlcBufRcvdFnc: data=6E127228, len=14,
parseState[n,v]=[0,0], status= RCVD
MODEMDRV-7/4: data =
NO CARRIER
And some more detailed output:
MDIALOUT-7/4: >> CURR state=Await_Off_Hook, NEW event=Event_Off_Hook
MDIALOUT-7/4: decode timer started.
MDIALOUT-7/4: << NEW state=Await_Digits
MDIALOUT-7:4: parseForDial received 11 bytes
10 10 10 10 10 10 10 10 10 10 38
MDIALOUT-7:4: parseForDial: NORMAL -> IN_START
MDIALOUT-7:4: parseForDial: IN_START -> SUCKING_NUMBER (10)
MDIALOUT-7/4: >> CURR state=Await_Digits, NEW event=Event_Decoded_Digits
MDIALOUT-7/4: << NEW state=Await_Digits
MDIALOUT-7:4: parseForDial received 1 bytes
32
MDIALOUT-7/4: >> CURR state=Await_Digits, NEW event=Event_Decoded_Digits
MDIALOUT-7/4: << NEW state=Await_Digits
MDIALOUT-7:4: parseForDial received 1 bytes
(same thing repeated with 37, 34, 34, 38, 38, 38)
25 38
MDIALOUT-7:4: parseForDial: SUCKING_NUMBER -> SAW_SEPARATOR (8)
MDIALOUT-7/4: >> CURR state=Await_Digits, NEW event=Event_Decoded_Digits
MDIALOUT-7/4: << NEW state=Await_Digits
MDIALOUT-7:4: parseForDial received 10 bytes
10 10 10 10 10 10 10 10 10 10
MDIALOUT-7:4: parseForDial: SAW_SEPARATOR -> IN_END
MDIALOUT-7:4: parseForDial: IN_END -> GOT_ONE (10)
MDIALOUT-7:4: parseForDial: GOT_ONE -> NORMAL
MDIALOUT-7/4: stopping decode timer.
MDIALOUT-7/4: Initiaiting Dialing=82744888
MDIALOUT-7/4: >> CURR state=Dialing_Out, NEW event=Event_Call_Is_Up
MDIALOUT-7/4: << NEW state=Disabled
MDIALOUT-7/4: >> CURR state=Disabled, NEW event=Event_Close_Rqst
MDIALOUT-?/?: << NEW state= <DELETED>
MDIALOUT-7/4: >> CURR state=Await_Off_Hook, NEW event=Event_Off_Hook
MDIALOUT-7/4: decode timer started.
MDIALOUT-7/4: << NEW state=Await_Digits
MDIALOUT-7/4: >> CURR state=Await_Digits, NEW event=Event_Time_Out
MDIALOUT-7/4: << NEW state=Await_On_Hook
(then just sits here, giving a time_out every couple of seconds)
--
Kerrin Pine (kerrinp@chariot.net.au)
Technical Manager | Web: http://www.chariot.net.au/
Chariot Internet | Ph : (08) 8272 7677
214 Greenhill Road, EASTWOOD SA 5053 | Fax: (08) 8272 7210
"I stayed up all night playing poker with tarot cards. I got
a full house and four people died." -- Steven Wright
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: