Specifications
349
Log Posting Format
Table 52: Log Posting Capcode Letters
Overdialed And Call Recycle Posting
Log posting of trunk types has been expanded to indicate overdialed and call recycled 
numbers. A trailing “O” in the trunk column of the log report indicates overdialed and a 
trailing “R” indicates recycled. This change is useful for traffic monitoring applications. 
For example, a trunk might be reported as “12AO”, meaning that the page was overdialed 
on (DID) trunk 12A. In addition, if the call recycle option were activated after the first 
page was entered, the second (and any later pages) would post as “12AR”. In previous 
ZPAGE versions, both of these calls would post as “12AL”. 
New Destination Type (Log +)
A new log destination type was created. The new destination, specified in the 
network.cus file, is labeled “Log+”. The new label does not actually send a page, it just 
log posts for diagnostic purposes. Here are several examples of the new log postings: 
Inbound CAP 1212 * * 1 3 Log+
Inbound CAP 3333 * * 1 3 1/OS Log+
Outbound TEST 2 Log+
The first example shows a log of just the TNPP destination. The second example shows a 
page and an extra log. The third example has a dummy destination, and it only log posts. 
The new “Log+” destination is useful for observing the delay in sending a page. In 
addition, it makes it easy to check capcodes on TNPP traffic that you do not want to page 
locally. 
Pager Format Letter TNPP notes
2-tone 2
5/6-tone 5
Blick B
DP6000 D not supported; D=DTMF
Golay 
type IIA 
all others
T 
G 
HSC H
Multitone M uses “4”, “V”, & “6”
NEC D3 N
POCSAG 
512 baud 
1200 baud 
2400 baud
P 
p 
Q
Quick Call 1 Q not supported
RDS R










