Displaying 2 results from an estimated 2 matches for "72bd".
Did you mean:
722d
2003 Nov 05
0
SIP broken for budgtone.
...etries exceeded on call d21f4608-1b1f-0a52-b657-2d9ca6239169@192.168.1.223 for seqno 1735 (Response)
With sip debug
Sip read:
INVITE sip:9998@192.168.1.2 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.223 From: "William Carlson" <sip:budgtone@192.168.1.2>;tag=ab86b88b-d30d-4b9a-8cfe-f143b09372bd To: <sip:9998@192.168.1.2> Contact: <sip:budgtone@192.168.1.223> Call-ID: fd9e49e7-81fe-9a6d-7b39-69b0b88bce52@192.168.1.223 CSeq: 62159 INVITE User-Agent: Grandstream SIP UA 1.0.3.81 Max-Forwards: 70 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE Content-Type:...
2004 Sep 24
1
sharing /etc/passwd
How 'bout PAM? /usr/ports/security/pam_ldap. If you have machines that
can't do PAM, perhaps NIS is the way to go (assuming, of course, you're
behind a firewall). You can store login information in LDAP like you want,
then use a home-grown script to extract the information to a NIS map. Or,
if you have a Solaris 8 machine lying around, you can cut out the middle
step and use