| Author |
Message |
Tim
Guest
|
 Posted:
Tue Jan 04, 2005 2:01 am Post subject:
Conversations not going through using an access proxy |
|
|
Alright so my outside users are on TLS with an access proxy, my inside
users are on auto config tcp. Now tls users can start a conversation
with tcp users no problem everything works. But if a tcp users wants to
start a conversation with a tls user the message never goes through. No
error, just never shows up on the other end |
|
| Back to top |
|
 |
Bob Christian
Guest
|
| Posted:
Tue Jan 04, 2005 9:02 am Post subject:
Re: Conversations not going through using an access proxy |
|
|
Tim:
I have seen the same thing in a lab environment when attempting to setup
federation. With some help from Microsoft we discovered that the solution
was to use TLS on both ends. This may not be acceptable for you, but it
worked for me.
This may be something that needs to be tracked as a bug. If you look at the
SIP headers on the server, the message will make it across the proxy, but
will die before going to the client.
Bob
"Tim" <none@none.com> wrote in message
news:%23DtZP8c8EHA.1228@tk2msftngp13.phx.gbl...
| Quote: | Alright so my outside users are on TLS with an access proxy, my inside
users are on auto config tcp. Now tls users can start a conversation
with tcp users no problem everything works. But if a tcp users wants to
start a conversation with a tls user the message never goes through. No
error, just never shows up on the other end |
|
|
| Back to top |
|
|
Tim
Guest
|
| Posted:
Tue Jan 04, 2005 10:38 pm Post subject:
Re: Conversations not going through using an access proxy |
|
|
Bob Christian wrote:
| Quote: | Tim:
I have seen the same thing in a lab environment when attempting to setup
federation. With some help from Microsoft we discovered that the solution
was to use TLS on both ends. This may not be acceptable for you, but it
worked for me.
This may be something that needs to be tracked as a bug. If you look at the
SIP headers on the server, the message will make it across the proxy, but
will die before going to the client.
Bob
"Tim" <none@none.com> wrote in message
news:%23DtZP8c8EHA.1228@tk2msftngp13.phx.gbl...
Alright so my outside users are on TLS with an access proxy, my inside
users are on auto config tcp. Now tls users can start a conversation
with tcp users no problem everything works. But if a tcp users wants to
start a conversation with a tls user the message never goes through. No
error, just never shows up on the other end
The problem though also includes TLS users not being able to talk to TLS |
users so I don't think that your solution will work. |
|
| Back to top |
|
|
Bob Christian
Guest
|
| Posted:
Wed Jan 05, 2005 2:51 am Post subject:
Re: Conversations not going through using an access proxy |
|
|
Yikes! That is not good. I have not seen that one yet.
"Tim" <none@none.com> wrote in message
news:e1oOWvn8EHA.1400@TK2MSFTNGP11.phx.gbl...
| Quote: | Bob Christian wrote:
Tim:
I have seen the same thing in a lab environment when attempting to setup
federation. With some help from Microsoft we discovered that the
solution
was to use TLS on both ends. This may not be acceptable for you, but it
worked for me.
This may be something that needs to be tracked as a bug. If you look at
the
SIP headers on the server, the message will make it across the proxy,
but
will die before going to the client.
Bob
"Tim" <none@none.com> wrote in message
news:%23DtZP8c8EHA.1228@tk2msftngp13.phx.gbl...
Alright so my outside users are on TLS with an access proxy, my inside
users are on auto config tcp. Now tls users can start a conversation
with tcp users no problem everything works. But if a tcp users wants to
start a conversation with a tls user the message never goes through. No
error, just never shows up on the other end
The problem though also includes TLS users not being able to talk to TLS
users so I don't think that your solution will work. |
|
|
| Back to top |
|
|
Dhigha D Sekara
Guest
|
| Posted:
Wed Jan 05, 2005 5:35 pm Post subject:
Re: Conversations not going through using an access proxy |
|
|
I am guessing it is not related to TLS/TCP.
It looks like any inside user is not able to initiate a call to the outside
user
Can you explain the topology you have?
looks like some kind of routing issue with the inside to ouside...
Can you post the client side tracing of the inside user?
To enable tracing, go to registry and under
- HKEY_CURRENT_USER\Software\Microsoft\Tracing\RTCDLL ( if you dont find
the key under HKCU, it should be in HKLM)
- EnableFileTracing key to 1.
- Restart the LCclient app and log should be under %userprofile%\tracing.
thanks, dhigha
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup
"Bob Christian" <BobChristian@removethis.gmail.com> wrote in message
news:Of5hy9p8EHA.4072@TK2MSFTNGP10.phx.gbl...
| Quote: | Yikes! That is not good. I have not seen that one yet.
"Tim" <none@none.com> wrote in message
news:e1oOWvn8EHA.1400@TK2MSFTNGP11.phx.gbl...
Bob Christian wrote:
Tim:
I have seen the same thing in a lab environment when attempting to
setup
federation. With some help from Microsoft we discovered that the
solution
was to use TLS on both ends. This may not be acceptable for you, but
it
worked for me.
This may be something that needs to be tracked as a bug. If you look
at
the
SIP headers on the server, the message will make it across the proxy,
but
will die before going to the client.
Bob
"Tim" <none@none.com> wrote in message
news:%23DtZP8c8EHA.1228@tk2msftngp13.phx.gbl...
Alright so my outside users are on TLS with an access proxy, my inside
users are on auto config tcp. Now tls users can start a conversation
with tcp users no problem everything works. But if a tcp users wants
to
start a conversation with a tls user the message never goes through.
No
error, just never shows up on the other end
The problem though also includes TLS users not being able to talk to TLS
users so I don't think that your solution will work.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in