Detection of Modem on AS5350

Discussion in 'Cisco' started by k.tragant@gmx.de, Jan 13, 2005.

  1. Guest

    Hello list,

    I've configured an AS5350 for incoming calls, for both: ISDN and analog
    modems. Everything works, but sometimes it seems that there is an
    incoming ISDN call and the AS5350 tries to negotiate an analog protocol
    (initial rx/tx-rate is 64000 (CALLTRKR-6-CALL_RECORD), but afterwards
    there is an analog modem negotiation (CALLTRKR-6-MODEM_CALL_REC)).
    Below you find an example output of Calltracker. We use IOS 12.3-3f
    (plan to upgrade to 12.3-12). For an answer I thank you in advance.

    Regards
    Kurt Tragant

    Output of a "normal" analog modem connection:

    Jan 8 22:48:23 192.168.110.21 3625: Jan 8 22:48:23.631:
    %CALLTRKR-6-CALL_RECORD: ct_hndl=2213, service=PPP, origin=Answer,
    category=Modem, DS0 slot/port/d
    s1/chan=3/0/0/19, called=12345, calling=23456, resource slot/port=1/66,
    userid=someuser, ip=1.2.3.4, mask=
    0.0.0.0, account id=5160, setup=01/08/2005 22:22:44, conn=0.05,
    phys=22.04, service=22.70, authen=22.70, init-rx/tx b-rate=28800/44000,
    rx/tx chars=215388/4
    386589, time=1534.06, disc subsys=ISDN, disc code=0x10, disc
    text=Normal call clearing
    Jan 8 22:48:24 192.168.110.21 3626: Jan 8 22:48:23.631:
    %CALLTRKR-6-MODEM_CALL_REC: ct_hndl=2213, prot: last=LAP-M,
    attempt=LAP-M, comp: last=V.42bis-Both
    , atmp= V.42bis-RX V.42bis-TX, std: last=V.90, attempt=V.90, init=V.90,
    snr=40, sq=7, rx/tx: chars=215388/4386589, ec: rx/tx=10772/32985, rx
    bad=4, rx/tx b-
    rate: last=28800/44000, low=28800/42667, high=28800/45333,
    desired-client=0/28800, desired-host=45333/28800, retr: local=0,
    remote=0, fail=0, speedshift: lo
    cal up/down=0/0, remote up/down=3/2, fail=0, v90: stat=Success,
    client=USR, fail=None, time(sec)=1513, disc reason=0x220

    Output of a weird connection (maybe ISDN which was treated as analog
    modem):

    Jan 8 23:18:04 192.168.110.21 3651: Jan 8 23:18:04.122:
    %CALLTRKR-6-CALL_RECORD: ct_hndl=2242, service=None, origin=Answer,
    category=Modem, DS0 slot/port/
    ds1/chan=3/0/0/1, called=12345, calling=(n/a), resource slot/port=1/93,
    userid=(n/a), ip=0.0.0.0, mask=0.0.0.0, account id=5236,
    setup=01/08/2005 23:17:1
    9, conn=0.05, phys=0.00, service=0.00, authen=0.00, init-rx/tx
    b-rate=64000/64000, rx/tx chars=0/0, time=33.09, disc subsys=ISDN, disc
    code=0x10, disc text=
    Normal call clearing
    Jan 8 23:18:05 192.168.110.21 3652: Jan 8 23:18:04.122:
    %CALLTRKR-6-MODEM_CALL_REC: ct_hndl=2242, prot: last=SYNC Mode,
    attempt=SYNC Mode, comp: last=None
    , atmp= None, std: last=V.21, attempt=V.21, init=V.21, snr=0, sq=0,
    rx/tx: chars=0/0, ec: rx/tx=0/0, rx bad=0, rx/tx b-rate:
    last=19200/48000, low=19200/480
    00, high=19200/48000, desired-client=0/19200, desired-host=26666/31200,
    retr: local=1, remote=0, fail=0, speedshift: local up/down=0/0, remote
    up/down=0/0,
    fail=0, v90: stat=Success, client=Rockwell, fail=None, time(sec)=12,
    disc reason=0x1F06
    , Jan 13, 2005
    #1
    1. Advertising

  2. No, this was no sync ISDN call that just "happened" to try to train
    as a modem. It was a real V.90 "Rockwell" (Conexant) modem.

    Aaron

    ---

    On 13 Jan 2005 04:51:54 -0800, wrote:

    ~ Hello list,
    ~
    ~ I've configured an AS5350 for incoming calls, for both: ISDN and analog
    ~ modems. Everything works, but sometimes it seems that there is an
    ~ incoming ISDN call and the AS5350 tries to negotiate an analog protocol
    ~ (initial rx/tx-rate is 64000 (CALLTRKR-6-CALL_RECORD), but afterwards
    ~ there is an analog modem negotiation (CALLTRKR-6-MODEM_CALL_REC)).
    ~ Below you find an example output of Calltracker. We use IOS 12.3-3f
    ~ (plan to upgrade to 12.3-12). For an answer I thank you in advance.
    ~
    ~ Regards
    ~ Kurt Tragant
    ~
    ~ Output of a "normal" analog modem connection:
    ~
    ~ Jan 8 22:48:23 192.168.110.21 3625: Jan 8 22:48:23.631:
    ~ %CALLTRKR-6-CALL_RECORD: ct_hndl=2213, service=PPP, origin=Answer,
    ~ category=Modem, DS0 slot/port/d
    ~ s1/chan=3/0/0/19, called=12345, calling=23456, resource slot/port=1/66,
    ~ userid=someuser, ip=1.2.3.4, mask=
    ~ 0.0.0.0, account id=5160, setup=01/08/2005 22:22:44, conn=0.05,
    ~ phys=22.04, service=22.70, authen=22.70, init-rx/tx b-rate=28800/44000,
    ~ rx/tx chars=215388/4
    ~ 386589, time=1534.06, disc subsys=ISDN, disc code=0x10, disc
    ~ text=Normal call clearing
    ~ Jan 8 22:48:24 192.168.110.21 3626: Jan 8 22:48:23.631:
    ~ %CALLTRKR-6-MODEM_CALL_REC: ct_hndl=2213, prot: last=LAP-M,
    ~ attempt=LAP-M, comp: last=V.42bis-Both
    ~ , atmp= V.42bis-RX V.42bis-TX, std: last=V.90, attempt=V.90, init=V.90,
    ~ snr=40, sq=7, rx/tx: chars=215388/4386589, ec: rx/tx=10772/32985, rx
    ~ bad=4, rx/tx b-
    ~ rate: last=28800/44000, low=28800/42667, high=28800/45333,
    ~ desired-client=0/28800, desired-host=45333/28800, retr: local=0,
    ~ remote=0, fail=0, speedshift: lo
    ~ cal up/down=0/0, remote up/down=3/2, fail=0, v90: stat=Success,
    ~ client=USR, fail=None, time(sec)=1513, disc reason=0x220
    ~
    ~ Output of a weird connection (maybe ISDN which was treated as analog
    ~ modem):
    ~
    ~ Jan 8 23:18:04 192.168.110.21 3651: Jan 8 23:18:04.122:
    ~ %CALLTRKR-6-CALL_RECORD: ct_hndl=2242, service=None, origin=Answer,
    ~ category=Modem, DS0 slot/port/
    ~ ds1/chan=3/0/0/1, called=12345, calling=(n/a), resource slot/port=1/93,
    ~ userid=(n/a), ip=0.0.0.0, mask=0.0.0.0, account id=5236,
    ~ setup=01/08/2005 23:17:1
    ~ 9, conn=0.05, phys=0.00, service=0.00, authen=0.00, init-rx/tx
    ~ b-rate=64000/64000, rx/tx chars=0/0, time=33.09, disc subsys=ISDN, disc
    ~ code=0x10, disc text=
    ~ Normal call clearing
    ~ Jan 8 23:18:05 192.168.110.21 3652: Jan 8 23:18:04.122:
    ~ %CALLTRKR-6-MODEM_CALL_REC: ct_hndl=2242, prot: last=SYNC Mode,
    ~ attempt=SYNC Mode, comp: last=None
    ~ , atmp= None, std: last=V.21, attempt=V.21, init=V.21, snr=0, sq=0,
    ~ rx/tx: chars=0/0, ec: rx/tx=0/0, rx bad=0, rx/tx b-rate:
    ~ last=19200/48000, low=19200/480
    ~ 00, high=19200/48000, desired-client=0/19200, desired-host=26666/31200,
    ~ retr: local=1, remote=0, fail=0, speedshift: local up/down=0/0, remote
    ~ up/down=0/0,
    ~ fail=0, v90: stat=Success, client=Rockwell, fail=None, time(sec)=12,
    ~ disc reason=0x1F06
    Aaron Leonard, Jan 14, 2005
    #2
    1. Advertising

  3. Guest

    Hi Aaron,

    > No, this was no sync ISDN call that just "happened" to try to train
    > as a modem. It was a real V.90 "Rockwell" (Conexant) modem.


    but why the init-rx/tx b-rate is 64000/64000 ? It's normal?
    Regards
    Kurt
    , Jan 17, 2005
    #3
  4. On 17 Jan 2005 02:56:08 -0800, wrote:

    ~ Hi Aaron,
    ~
    ~ > No, this was no sync ISDN call that just "happened" to try to train
    ~ > as a modem. It was a real V.90 "Rockwell" (Conexant) modem.
    ~
    ~ but why the init-rx/tx b-rate is 64000/64000 ? It's normal?
    ~ Regards
    ~ Kurt

    This is the initial tx/rx rate reported by Call Tracker at the
    ISDN layer. If the call had successfully trained in a modem
    modulation, then these values would have been replaced with the
    "real" modem tx/rx rates, but this call failed to train.

    Aaron
    Aaron Leonard, Jan 17, 2005
    #4
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Aaron Leonard

    Re: AS5350 reverse telnet

    Aaron Leonard, Jul 10, 2003, in forum: Cisco
    Replies:
    0
    Views:
    1,620
    Aaron Leonard
    Jul 10, 2003
  2. bod

    AS5200- AS5350 Problem

    bod, Jul 10, 2003, in forum: Cisco
    Replies:
    1
    Views:
    990
    Aaron Leonard
    Jul 10, 2003
  3. Darren
    Replies:
    0
    Views:
    979
    Darren
    Dec 3, 2003
  4. Brian Jones
    Replies:
    1
    Views:
    4,959
    shido
    Aug 8, 2003
  5. Chad

    Modem Detection

    Chad, Mar 17, 2006, in forum: Computer Support
    Replies:
    9
    Views:
    500
    Plato
    Mar 18, 2006
Loading...

Share This Page