Pages

2/26/2004

2/25/2004

Telecom::VoIP::FXS and FXO Interfaces



What is an FXS interface vs FXO interface?

FXS = Foreign Exchange Subscriber = "client" - controls "off hook"

FXO = Foreign Exchange Office = "server" - provides power, controls everything else.

When making a connection from a telephone system to another device this distinction is important.

http://www.patton.com/technotes/fxs_fxo.pdf has a very good discussion about this.

It boils down to the same thing as a similar interface and pinout discussions - consider null-modem cables and crossover ethernet cables
This category of topic came way back when I wanted to setup my "normal" PC devices to print to my DEC laser printers that I used with the PDP-11. (Until "progress" required we replace it with the slow, piddly Laserjet-III......) Had to have a serial cable custom built so that all the right pins on one side would talk to all the right pins on the other.

Cisco Firewall::FILTERing URL's::Long URL's


Also had some curious issues with AOL mail logon.
Alleviated when I added the following to the end of the filter url line:
longurl-truncate cgi-truncate

2/20/2004

Cisco Firewall::FILTERing URL's::Westlaw

Updated
Using either N2H2 or Websense content filtering server with the Cisco firewall (v6.3.3) url-server and filter url commands is a great way to employ URL filtering to objectionable sites. However we experienced a strange issue with Westlaw's research site. At www.westlaw.com users logon and do legal research and choose to print. Interestingly, the printing happens on WestLaw provided printers that are "attached" to the Westlaw service network via modems. Even though this printing is "internal" to Westlaw some print jobs fail for some reason when using url filtering on the firewall. It must create some really odd url to launch the print job and some of these url's must be crapping out at the firewall and/or the content filtering server.
A while back in an attempt to implement this filtering a problem arose with long url's. According to the vendors the solution to this issue was to upgrade to latest firewal code. That has been done and those url's that brought this previous issue to light now are working fine. (logon to hotmail.com and transactions at airline reservation sites resulted in some wild-and long-urls.) But now we have this Westlaw thing.
The workaround to the immediate issue is to make an exception to the filter url statement for the following networks at Westlaw:
163.231.237.0/24
167.68.6.0/23
AND167.231.253.0/24

But I fear a deeper issue is learking in there waiting to arise in some situation that doesn't have a clear and simple workaround.

Exchange 2000::Windows 2000::Account Expiration


Had an odd problem recently with getting into an Exchange mailbox. A user's AD account was setup to expire at a certain date and time. When that time came she was logged on and working in her mailbox. Kaboom-she's kicked out at the appointed time. She tries to log back on and can't. All working as designed. If only the admin had setup the proper account to expire instead of this person who is now locked. No biggy: just re-enable the account in ADUC. Okay fine, now she can log on, but--holy crap!--can't get into Exchange.

Nor can anyone with full rights assigned to her mailbox get into it. Attempting to send an e-mail to that mailbox -> bounced message.

To get this to work I had to delete the exchange account (we have it setup so the mailbox is not really deleted for 30 days) and then relink the exchange account to the AD user.

Conclusion: Expiring accounts is a baaaaaad thing.

2/11/2004

DocsOpen UN-Integration::MSWord::Windows Registry


For MSWord and other applications using ODMA integration to DocsOpen (or other ODMA compliant DMS, if any...) ODMA is "activated" in the registry under:
[HKEY_CLASSES_ROOT\ODMA32]

If you remove that key and all it's subkeys then DMS is unintegrated.
This can be done by manually merging a registry file that looks like:
Windows Registry Editor Version 5.00

[-HKEY_CLASSES_ROOT\ODMA32]

Merging that file can be done in a BAT file with the line:
regedit /s [filename].REG


Webview::Windows XP::AD Logon


Continuing saga from previous posting....
When you use Webview interface to Elite time entry and passthrough authentication -
"Pre-Windows 2000" account must exactly match the Elite userid - also case sensitive
and
The case with which the user logs on does not matter (like it does for Elite.)

Elite::Windows XP::AD Logon


When security passes through XP/AD logon to Elite it is case sensitive and will fail if the user doesn't capitalize properly.
If the elite userid is all in lower case, then the user's "Pre-Windows 2000" account must be in all lower case AND the user must key in all lower case when they logon.
Of course if you have multiple "pass through" security applications that have this issue then you will have to change either the elite userid or the userid in the other application to match and then match that to the "Pre-Windows 2000" account.

Aint ya glad you use directory services.... Don't ya wish everybody did?