This patch, submitted by Sascha Herrmann <sascha.herrmann@gmx.de>, allows the
extended RING identifier to be configured. Apparently Zyxel sends extended
RING information in the format... "RING;
1234567890;12345". The default remains
the same, so existing configurations should encounter no problems.
else if (streq(conf.ringVoice, rbuf))
type = CALLTYPE_VOICE;
else {
- if (strneq(rbuf, "RING ", 5)) // extended RING
+ if (strneq(rbuf, conf.ringExtended,
+ conf.ringExtended.length())) // extended RING
n--;
conf.parseCID(rbuf, cinfo);
break;
{ "ringdata", &ModemConfig::ringData },
{ "ringfax", &ModemConfig::ringFax },
{ "ringvoice", &ModemConfig::ringVoice },
+{ "ringextended", &ModemConfig::ringExtended, "RING " },
{ "cidname", &ModemConfig::cidName },
{ "cidnumber", &ModemConfig::cidNumber },
};
fxStr ringData; // data call ring string
fxStr ringFax; // fax call ring string
fxStr ringVoice; // voice call ring string
+ fxStr ringExtended; // extended ring
// caller id
fxStr cidName; // pattern for name info
fxStr cidNumber; // pattern for number info
RecvDataFormat string \s-1adaptive\s+1 format for received facsimile data
RecvFileMode octal \s-10600\s+1 protection mode to use for received facsimile files
RingData string \- distinctive ring data call identifier
+RingExtended string \s-1"RING "\s+1 extended ring message identifier
RingFax string \- distinctive ring fax call identifier
RingsBeforeAnswer integer \s-10\s+1 rings to wait before answering phone
RingVoice string \- distinctive ring voice call identifier
and
.BR RingVoice .
.TP
+.B RingExtended
+An identifier which matches the initial portion of an extended RING
+message sent by the modem to relay CID and/or DNIS data instead of
+sending it formatted on separate lines.
+.TP
.B RingFax
A modem status string that identifies that an incoming call is
for facsimile use.