Hello, We consider adding instant messaging capability to one of our products and started experiments using the Microsoft Windows Messenger 5.0 and partysip 0.5.5-2 running on Windows workstations, all in the same LAN.
So far, the test were not successful at all: all our attempts to send a message from client 1 (C1) to client 2 (C2) using partysip as the SIP proxy (S) resulted in errors displayed in the Messenger window. When we use a packet sniffer to see the exchange between C1, C2 and S, it looks like everything goes according to this scenario: 1. C1 -> S: INVITE to C2 2. S -> C1: TRYING 3. S -> C2: INVITE from C1 4. C2 -> S: TRYING 5. C2 -> S: OK (answers to INVITE #3) 6. C2 -> C1: BYE (but why?) 7. C1 -> C2: 481 (answers to BYE; sure, the transaction does not exist) 8. C2 -> S: OK (answers to INVITE #3, appears to be a duplicate of #5) 9. S -> C1: OK (answers to INVITE #1) Why does the C2 send BYE to C1, though there was no active direct comms? Of course, this may be an issue with the MS Windows Messenger... In this case, can anyone recommend a command-line utility (Windows or any unix-like OS would be OK) which is expected to work with partysip or any other free SIP proxy server? Thank you in advance. -- Best regards, Dmitry Akindinov -- Stalker Labs. _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
