vgetty doesn't detect Elsa Microlink TLV.34

[Markus Schaub]

Hi,

Some newsgroup posts indicate that the Elsa Microlink TLV.34 works
together with vgetty, however mine doesn't even get detected as a voice
modem:

[...]
04/13 20:56:10 yS1 voice command: 'AT+FCLASS=8' -> 'OK'
04/13 20:56:10 yS1 vgetty: AT+FCLASS=8
04/13 20:56:10 yS1 serial port: OK
04/13 20:56:10 yS1 voice command: 'AT+VSM=1,8000' -> 'OK'
04/13 20:56:10 yS1 vgetty: AT+VSM=1,8000
04/13 20:56:10 yS1 serial port: ERROR
04/13 20:56:10 yS1 vgetty: Modem returned ERROR
04/13 20:56:10 yS1 voice command: 'AT+FCLASS=0' -> 'OK'
04/13 20:56:11 yS1 vgetty: AT+FCLASS=0
04/13 20:56:11 yS1 serial port: OK
04/13 20:56:11 yS1 no voice modem detected

Unfortunatly the modem manual doesn't include a list of the voice
commands. Can anybody give me a hint about getting vgetty detect the
modem or can give me some information of the tlv.34 voice command set?

Markus

[Juergen Kosel]

Post by Markus Schaub
Hi,
Some newsgroup posts indicate that the Elsa Microlink TLV.34 works
together with vgetty, however mine doesn't even get detected as a voice

What version of mgetty/vgetty do you use?

Post by Markus Schaub
[...]
04/13 20:56:10 yS1 voice command: 'AT+FCLASS=8' -> 'OK'
04/13 20:56:10 yS1 vgetty: AT+FCLASS=8
04/13 20:56:10 yS1 serial port: OK
04/13 20:56:10 yS1 voice command: 'AT+VSM=1,8000' -> 'OK'
04/13 20:56:10 yS1 vgetty: AT+VSM=1,8000

I believe, that the TLV.34 orgins from a time before the V.253
commandset was defined and ELSA modems supported the Rockwell AT#V voice
commandset and interrim standard 101.
Either we need to fix the source file detect.c so that the TLV.34 uses
the driver in Elsa.c or you use the
enable_compression_mapping_querry TRUE
setting from the current vgetty release.
Maybe you need to increase the loglevel of vgetty...


Greetings
Juergen

[Markus Schaub]

Post by Juergen Kosel

Post by Markus Schaub
Some newsgroup posts indicate that the Elsa Microlink TLV.34 works
together with vgetty, however mine doesn't even get detected as a voice

What version of mgetty/vgetty do you use?

vgetty: experimental test release 0.9.32 / with duplex patch
(It's from Debian stable, but it doesn't seem, that the Debian people
anything.)

Post by Juergen Kosel
Either we need to fix the source file detect.c so that the TLV.34 uses
the driver in Elsa.c or you use the enable_compression_mapping_querry
TRUE setting from the current vgetty release.

This didn't change anything.

Post by Juergen Kosel
Maybe you need to increase the loglevel of vgetty...

The loglevel ist already set to 6, but I will post a larger part of the
log:

[...]
| check for lockfiles
| checklock: no active process has lock, will remove
| locking the line
| makelock(ttyS1) called
| do_makelock: lock='/var/lock/LCK..ttyS1'
| lock made
| tio_get_rs232_lines: status: RTS CTS DSR DTR
| lowering DTR to reset Modem
| tss: set speed to 115200 (10002)
| tio_set_flow_control( HARD )
| waiting for line to clear (VTIME=1), read:
| send: \dATQ0V1H0[0d]
| waiting for ``OK''
| got: [0d][0a]OK ** found **
| send: AT[0d]
| waiting for ``OK''
| got: [0d]
| CND: OK[0a][0d][0a]OK ** found **
| mdm_send: 'ATI'
| got:[0d][0a][0d][0a]643[0d]
| mdm_gis: string 1: '643'
| got:[0a][0d][0a]OK[0d]
| mdm_identify: string '643'
| ELSA MicroLink ISDN/TLV.34 detected
| mdm_send: 'ATI3'
| got:[0a][0d][0a]Ver. 3.00J vom 24.07.1998 P[0d]
| mdm_gis: string 1: 'Ver. 3.00J vom 24.07.1998 P'
| got:[0a][0d][0a]OK[0d]
| additional info: 'Ver. 3.00J vom 24.07.1998 P'
| mdm_send: 'AT+FCLASS=2.0'
| got:[0a][0d][0a]OK[0d]
| mdm_command: string 'OK' -> OK
| mdm_send: 'AT+FAA=1;+FCR=1'
| got:[0a][0d][0a]OK[0d]
| mdm_command: string 'OK' -> OK
| mdm_send: 'AT+FBO=1'
| got:[0a][0d][0a]OK[0d]
| mdm_command: string 'OK' -> OK
| mdm_send: 'AT+FNR=1,1,1,0'
| got:[0a][0d][0a]OK[0d]
| mdm_command: string 'OK' -> OK
| mdm_send: 'AT+FLI="+49 911 XXXXXXXX"'
| got:[0a][0d][0a]OK[0d]
| mdm_command: string 'OK' -> OK
| mdm_send: 'AT+FCC=1,5,0,2,0,0,0,0'
| got:[0a][0d][0a]OK[0d]
| mdm_command: string 'OK' -> OK
| tss: set speed to 38400 (017)
| tss: set speed to 38400 (017)
| tio_set_flow_control( HARD )
| detecting voice modem type
| vgetty: ATE0
| serial port: OK
| voice command: 'ATI9' -> ''
| vgetty: ATI9
| serial port: ([01]#ELS0326\00000562\MODEM\TIA0602,TIA0578,TIA0592\MicroLink ISDN/TLV.3400)
| PNP String: 'ELS0326\00000562\MODEM\TIA0602,TIA0578,TIA0592\MicroLink ISDN/TLV.3400)'
| checking pnpid SUP / modelid <none>
| checking pnpid ZYX / modelid 02FF
| checking pnpid USR / modelid 0088
| checking pnpid ELS / modelid 0687
| checking pnpid ELS / modelid 0566
| checking pnpid ELS / modelid 0707
| checking pnpid ELS / modelid 8318
| checking pnpid ELS / modelid 0853
| checking pnpid ELS / modelid 8548
| checking pnpid ELS / modelid 0754
| checking pnpid ELS / modelid 0350
| checking pnpid ELS / modelid 0503
| checking pnpid ELS / modelid 0667
| checking pnpid ELS / modelid 0152
| checking pnpid ELS / modelid 0363
| checking pnpid ELS / modelid 0862
| checking pnpid ELS / modelid 6026
| checking pnpid ELS / modelid 6027
| serial port: OK
| voice command: 'ATI3' -> ''
| vgetty: ATI3
| serial port: Ver. 3.00J vom 24.07.1998 P
| serial port: OK
| voice command: 'ATI' -> ''
| vgetty: ATI
| serial port: 643
| serial port: OK
| voice command: 'AT+FCLASS=8' -> 'OK'
| vgetty: AT+FCLASS=8
| serial port: OK
| voice command: 'AT+VSM=1,8000' -> 'OK'
| vgetty: AT+VSM=1,8000
| serial port: ERROR
| vgetty: Modem returned ERROR
| voice command: 'AT+FCLASS=0' -> 'OK'
| vgetty: AT+FCLASS=0
| serial port: OK
| no voice modem detected

Regards,
Markus

[Gert Doering]

Hi,

Post by Juergen Kosel
{"ELS", "0362", &ISDN4Linux, "ELSA Microlink TLV.34" },

Does the TLV use the same command set as i4l? Would surprise me :-)

gert

[Juergen Kosel]

Post by Gert Doering
Hi,

Post by Juergen Kosel
{"ELS", "0362", &ISDN4Linux, "ELSA Microlink TLV.34" },

Does the TLV use the same command set as i4l? Would surprise me :-)

I guess the TLV.34 supports the ISDN capi.
But it might be a waste of computing power, if a kernel module is used
to emulate a standard modem but the TLV.34 already contains a standard
modem.


Greetings
Juergen

[Gert Doering]

Hi,

Post by Juergen Kosel

Post by Gert Doering

Post by Juergen Kosel
{"ELS", "0362", &ISDN4Linux, "ELSA Microlink TLV.34" },

Does the TLV use the same command set as i4l? Would surprise me :-)

I guess the TLV.34 supports the ISDN capi.

It does? Interesting. I know that the ZyXEL 2864I can do CAPI (very much
undocumented), but didn't know that about the TLV.34.

I'm not sure whether linux modules exist to use the CAPI interface of
the TLV.34, though.

Post by Juergen Kosel
But it might be a waste of computing power, if a kernel module is used
to emulate a standard modem but the TLV.34 already contains a standard
modem.

Indeed.

gert

[Juergen Kosel]

Post by Markus Schaub
| voice command: 'ATI9' -> ''
| vgetty: ATI9
| serial port: ([01]#ELS0326\00000562\MODEM\TIA0602,TIA0578,TIA0592\MicroLink ISDN/TLV.3400)
| PNP String: 'ELS0326\00000562\MODEM\TIA0602,TIA0578,TIA0592\MicroLink ISDN/TLV.3400)'
| checking pnpid SUP / modelid <none>
| checking pnpid ZYX / modelid 02FF
| checking pnpid USR / modelid 0088
| checking pnpid ELS / modelid 0687
| checking pnpid ELS / modelid 0566
| checking pnpid ELS / modelid 0707
| checking pnpid ELS / modelid 8318
| checking pnpid ELS / modelid 0853
| checking pnpid ELS / modelid 8548
| checking pnpid ELS / modelid 0754
| checking pnpid ELS / modelid 0350
| checking pnpid ELS / modelid 0503
| checking pnpid ELS / modelid 0667
| checking pnpid ELS / modelid 0152
| checking pnpid ELS / modelid 0363
| checking pnpid ELS / modelid 0862
| checking pnpid ELS / modelid 6026
| checking pnpid ELS / modelid 6027
| serial port: OK

obviously the modem is not detected.
So what you can do is:
- get the sources of mgetty (they include vgetty)
- in mgettysourcedir/voice/libvoice/detect.c you will find

static const struct pnp_modem_type_struct pnp_modem_database[] =
{
{"SUP", NULL, &Supra, "SupraFAX modem (generic)" },
{"ZYX", "02FF", &ZyXEL_2864, "ZyXEL 2864I (DSS1)" },
{"USR", "0088", &US_Robotics, "U.S. Robotics 56k Message" },
{"ELS", "0687", &Elsa, "ELSA ML 56k DE" },
{"ELS", "0566", &Elsa, "ELSA ML 56k CH" },
{"ELS", "0707", &Elsa, "ELSA ML 56k AT" },
{"ELS", "8318", &Elsa, "ELSA ML 56k pro" },
{"ELS", "0853", &Elsa, "ELSA/1&1 Speedmaster pro" },
{"ELS", "8548", &Elsa, "ELSA ML Office" },
{"ELS", "0754", &Elsa, "ELSA ML 56k basic" },
{"ELS", "0350", &Elsa, "ELSA ML 56k internet" },
{"ELS", "0503", &Elsa, "ELSA ML 56k internet" },
{"ELS", "0667", &Elsa, "ELSA ML 56k internet" },
{"ELS", "0152", &Elsa, "ELSA ML 56k internet c" },
{"ELS", "0363", &V253modem, "ELSA ML 56k fun" },
{"ELS", "0862", &V253modem, "ELSA MicroLink 56k Internet II" },
{"ELS", "6026", &V253modem, "ELSA ML 56k Fun II a" },
{"ELS", "6027", &V253modem, "ELSA ML 56k Fun II c" },
{NULL, NULL, NULL}
};

add
{"ELS", "0362", &Elsa, "ELSA Microlink TLV.34" },
above the terminating {NULL, NULL, NULL} entry.
Then build mgetty and vgetty and replace vgetty what you had already
installed.
If you want to avoid trouble finding the correct config files, I
recommend that you take the sources from Debian source archive and build
a .deb packet for vgetty.

Since the TLV.34 is both, analog and ISDN, you could also try:
{"ELS", "0362", &ISDN4Linux, "ELSA Microlink TLV.34" },


Greetings
Juergen