Thursday, November 06, 2008 2:40 PMWe are currently deploying a edge server to complement our internal OCS server, but we are unable to connect externally. The edge is directly routable from the internet by using a 'no nat' rule in our Cisco PIX, but when running the Validation on the Edge, we get the following error:
Received a failure SIP response: User sip:email@example.com @ Server ocs.domain.com
Received a failure SIP response: [
SIP/2.0 504 Server time-out
CSEQ: 7 INVITE
VIA: SIP/2.0/TLS 172.16.137.50:1362;branch=z9hG4bKb3d8b98b;ms-received-port=1362;ms-received-cid=C9700
AUTHENTICATION-INFO: NTLM rspauth="01000000B0644F03ECFA8EFD1C90D270", srand="69BECE0D", snum="3", opaque="99C3E390", qop="auth", targetname="vm-mansrvocs.domain.local", realm="SIP Communications Service"
ms-diagnostics: 1022;reason="Cannot process routing destination";source="vm-mansrvocs.domain.local";Destination="sip:firstname.lastname@example.org:5061;maddr=ocs.domain.com;transport=tls"
I've seen another post with the same issue, but his suggested resolution is not applicable here. In that post, someone suggested running a 'sip stack trace' but i'm unsure as to how to do this. Can anyone advise on the stack trace, or possible causes of the above error?
Thursday, November 06, 2008 3:08 PMJust some additional detail, we can successfully telnet between the OCS and the Edge server on port 5061 and ping with no issues to FQDN's
Tuesday, November 18, 2008 3:23 PM
Same for me. Everything is fine. If anybody could help .....
Wednesday, November 19, 2008 10:06 PM
You can do a sip trace by doing a New Debug session
Right Click on the Pool or EDGE Server and Select new debug session
Select SIP & S4 in the list and look at the traces with the snooper tool from the OCS 2007 Resource Kit
Wednesday, March 04, 2009 5:50 PMcan anyone post the solution?
did a trace but couldn't get anything useful