Diego Marin
2007-11-07 18:58:27 UTC
Please look at the forum link I found below :
http://forums.microsoft.com/OCS2007/ShowPost.aspx?PostID=1412736&SiteID=57
If I specify the registry key below (Port Rage 50,000-59,999) on a client
PC. I am able to make calls from inside the network, ( while connected to
the internal server ) to an external users (connected to the Edge Server) .
However, the external user can not call me. (Seems to work only one way
????)
Registry Key Specified in the above link
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator\PortRange]
"Enabled"=dword:00000001
"MinMediaPort"=dword:0000c350
"MaxMediaPort"=dword:0000e678
What is the communication flow for a external user connected to the edge
server and an internal user connected to the Frond End Server.
My understanding is that all communication will be P2P if possible and if
not, it will try to communicate through the Edge server ????
Which means that this group policy should not be necessary if the Edge
Server is working properly ?
I am able to make phone calls with remote users but only when logging in
through the Edge Server.
If I login through the Front End Server, I am able to make calls with local
users (also connecting to the Frond End Server) but unable to make calls
with remote users.
If I run Validation of A/V Conferencing server from the front end server I
get the following failure.
Connecting to A/V Authentication Edge Server to get credentials
Exception: Unable to establish a connection
[0Xc3f200d] One or more errors were detected
This is what I get on the Remote PC when trying to make a call to the
internal PC
This message was not delivered to Diego Marin because it is too large:
Event Type: Warning
Event Source: Communicator
Event Category: None
Event ID: 11
Date: 11/6/2007
Time: 5:20:03 PM
User: N/A
Computer: REMORE
Description:
A SIP request made by Communicator failed in an unexpected manner (status
code 0). More information is contained in the following technical data:
RequestUri:
_sip:Usnshocedge01.gn.com:443;transport=tls;lr;ms-route-sig=ad-FQ9RaEsYGU2FOau4lcBC-0FmnpLea_U849OswAA
From: _sip:***@gn.com;tag=b60f183434
To: ***@gn.com;tag=9a19dd96b7
Call-ID: 435d9f0983064dd8bc3b93daa1314d5c
Content-type: application/sdp;call-type=audiovideo
v=0
o=- 0 0 IN IP4 205.244.41.253
s=session
c=IN IP4 205.244.41.253
b=CT:99980
t=0 0
m=audio 50671 RTP/AVP 114 111 112 115 116 4 8 0 97 101
k=base64:/YlzxoHcbigk4/NKxaF6YHMhulesAzLOWboRu7uTtTLrC9q3NiMQ4afcmS1j
a=candidate:UVIRvHgwspa1tyG+qJdIwAS9Vtv+X0MdyRTJ129LUPk 1
I6/IRbp6P35Dq1BRe/pnoQ UDP 0.890 207.145.65.2 57888
a=candidate:UVIRvHgwspa1tyG+qJdIwAS9Vtv+X0MdyRTJ129LUPk 2
I6/IRbp6P35Dq1BRe/pnoQ UDP 0.890 207.145.65.2 51440
a=candidate:7x6SVdWya4CfhXb23/84IcL0qTRnPELEU3mOxb/T2RQ 1
gx2J2iH8QpEq8m7PxoLEsQ TCP 0.190 205.244.41.253 55151
a=candidate:7x6SVdWya4CfhXb23/84IcL0qTRnPELEU3mOxb/T2RQ 2
gx2J2iH8QpEq8m7PxoLEsQ TCP 0.190 205.244.41.253 55151
a=candidate:EW/rPzPllQQRQpVUvyGE7L9s/VamPuuv0q48SaHIv1w 1
aGDWKDDmHGpPTl8ybyz9xQ UDP 0.490 205.244.41.253 50671
a=candidate:EW/rPzPllQQRQpVUvyGE7L9s/VamPuuv0q48SaHIv1w 2
aGDWKDDmHGpPTl8ybyz9xQ UDP 0.490 205.244.41.253 51653
a=candidate:QzSQv0jlP0qZL427cVICv6d+H3Ub5oQBVFqZu4hffQI 1
QOkBJar3Lj+9tf/2f4JHUA TCP 0.250 207.145.65.2 52032
a=candidate:QzSQv0jlP0qZL427cVICv6d+H3Ub5oQBVFqZu4hffQI 2
QOkBJar3Lj+9tf/2f4JHUA TCP 0.250 207.145.65.2 52032
a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80
inline+ryKZgVFGIEnPyWXohyMV4Ax2n2S7LVv0UGhtC4|2^31|1:1
a=crypto:2 AES_CM_128_HMAC_SHA1_80
inline:6/zGjvogsrTEq1lv1hDTl0p65rArNMMRrm9tDwUf|2^31|1:1
a=maxptime:200
a=rtcp:51653
a=rtpmap:114 x-msrta/16000
a=fmtp:114 bitrate=29000
a=rtpmap:111 SIREN/16000
a=fmtp:111 bitrate=16000
a=rtpmap:112 G7221/16000
a=fmtp:112 bitrate=24000
a=rtpmap:115 x-msrta/8000
a=fmtp:115 bitrate=11800
a=rtpmap:116 AAL2-G726-32/8000
a=rtpmap:4 G723/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:97 RED/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=encryptionptional
Response Data:
183 Session Progress
101 Progress Report
ms-diagnostics: 13004;reason="Request was proxied to one or more registered
endpoints";source="USNSHOFFCOMM01.office.communicator.com";appName="InboundRouting"
180 Ringing
0 (null)
Ms-client-diagnostics: 52031; reason="Call terminated on media connectivity
failure"
Resolution:
If this error continues to occur, please contact your network
administrator. The network administrator can use a tool like winerror.exe
from the Windows Resource Kit or lcserror.exe from the Office Communications
Server Resource Kit in order to interpret any error codes listed above.
For more information, see Help and Support Center at
_http://go.microsoft.com/fwlink/events.asp.
http://forums.microsoft.com/OCS2007/ShowPost.aspx?PostID=1412736&SiteID=57
If I specify the registry key below (Port Rage 50,000-59,999) on a client
PC. I am able to make calls from inside the network, ( while connected to
the internal server ) to an external users (connected to the Edge Server) .
However, the external user can not call me. (Seems to work only one way
????)
Registry Key Specified in the above link
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator\PortRange]
"Enabled"=dword:00000001
"MinMediaPort"=dword:0000c350
"MaxMediaPort"=dword:0000e678
What is the communication flow for a external user connected to the edge
server and an internal user connected to the Frond End Server.
My understanding is that all communication will be P2P if possible and if
not, it will try to communicate through the Edge server ????
Which means that this group policy should not be necessary if the Edge
Server is working properly ?
I am able to make phone calls with remote users but only when logging in
through the Edge Server.
If I login through the Front End Server, I am able to make calls with local
users (also connecting to the Frond End Server) but unable to make calls
with remote users.
If I run Validation of A/V Conferencing server from the front end server I
get the following failure.
Connecting to A/V Authentication Edge Server to get credentials
Exception: Unable to establish a connection
[0Xc3f200d] One or more errors were detected
This is what I get on the Remote PC when trying to make a call to the
internal PC
This message was not delivered to Diego Marin because it is too large:
Event Type: Warning
Event Source: Communicator
Event Category: None
Event ID: 11
Date: 11/6/2007
Time: 5:20:03 PM
User: N/A
Computer: REMORE
Description:
A SIP request made by Communicator failed in an unexpected manner (status
code 0). More information is contained in the following technical data:
RequestUri:
_sip:Usnshocedge01.gn.com:443;transport=tls;lr;ms-route-sig=ad-FQ9RaEsYGU2FOau4lcBC-0FmnpLea_U849OswAA
From: _sip:***@gn.com;tag=b60f183434
To: ***@gn.com;tag=9a19dd96b7
Call-ID: 435d9f0983064dd8bc3b93daa1314d5c
Content-type: application/sdp;call-type=audiovideo
v=0
o=- 0 0 IN IP4 205.244.41.253
s=session
c=IN IP4 205.244.41.253
b=CT:99980
t=0 0
m=audio 50671 RTP/AVP 114 111 112 115 116 4 8 0 97 101
k=base64:/YlzxoHcbigk4/NKxaF6YHMhulesAzLOWboRu7uTtTLrC9q3NiMQ4afcmS1j
a=candidate:UVIRvHgwspa1tyG+qJdIwAS9Vtv+X0MdyRTJ129LUPk 1
I6/IRbp6P35Dq1BRe/pnoQ UDP 0.890 207.145.65.2 57888
a=candidate:UVIRvHgwspa1tyG+qJdIwAS9Vtv+X0MdyRTJ129LUPk 2
I6/IRbp6P35Dq1BRe/pnoQ UDP 0.890 207.145.65.2 51440
a=candidate:7x6SVdWya4CfhXb23/84IcL0qTRnPELEU3mOxb/T2RQ 1
gx2J2iH8QpEq8m7PxoLEsQ TCP 0.190 205.244.41.253 55151
a=candidate:7x6SVdWya4CfhXb23/84IcL0qTRnPELEU3mOxb/T2RQ 2
gx2J2iH8QpEq8m7PxoLEsQ TCP 0.190 205.244.41.253 55151
a=candidate:EW/rPzPllQQRQpVUvyGE7L9s/VamPuuv0q48SaHIv1w 1
aGDWKDDmHGpPTl8ybyz9xQ UDP 0.490 205.244.41.253 50671
a=candidate:EW/rPzPllQQRQpVUvyGE7L9s/VamPuuv0q48SaHIv1w 2
aGDWKDDmHGpPTl8ybyz9xQ UDP 0.490 205.244.41.253 51653
a=candidate:QzSQv0jlP0qZL427cVICv6d+H3Ub5oQBVFqZu4hffQI 1
QOkBJar3Lj+9tf/2f4JHUA TCP 0.250 207.145.65.2 52032
a=candidate:QzSQv0jlP0qZL427cVICv6d+H3Ub5oQBVFqZu4hffQI 2
QOkBJar3Lj+9tf/2f4JHUA TCP 0.250 207.145.65.2 52032
a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80
inline+ryKZgVFGIEnPyWXohyMV4Ax2n2S7LVv0UGhtC4|2^31|1:1
a=crypto:2 AES_CM_128_HMAC_SHA1_80
inline:6/zGjvogsrTEq1lv1hDTl0p65rArNMMRrm9tDwUf|2^31|1:1
a=maxptime:200
a=rtcp:51653
a=rtpmap:114 x-msrta/16000
a=fmtp:114 bitrate=29000
a=rtpmap:111 SIREN/16000
a=fmtp:111 bitrate=16000
a=rtpmap:112 G7221/16000
a=fmtp:112 bitrate=24000
a=rtpmap:115 x-msrta/8000
a=fmtp:115 bitrate=11800
a=rtpmap:116 AAL2-G726-32/8000
a=rtpmap:4 G723/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:97 RED/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=encryptionptional
Response Data:
183 Session Progress
101 Progress Report
ms-diagnostics: 13004;reason="Request was proxied to one or more registered
endpoints";source="USNSHOFFCOMM01.office.communicator.com";appName="InboundRouting"
180 Ringing
0 (null)
Ms-client-diagnostics: 52031; reason="Call terminated on media connectivity
failure"
Resolution:
If this error continues to occur, please contact your network
administrator. The network administrator can use a tool like winerror.exe
from the Windows Resource Kit or lcserror.exe from the Office Communications
Server Resource Kit in order to interpret any error codes listed above.
For more information, see Help and Support Center at
_http://go.microsoft.com/fwlink/events.asp.