Sinjo S Barakati | 18 Aug 06:35

OCS-sipX

Hello,

 

 

I am integrating OCS and sipX. I have a problem which the calls both direction can not established/not ringing at both end-point.

1.       OCS to sipX. When calling sipx to OCS below the debug I capture on Mediation. Supposed TO is to sipX which the IP <at> 172.18.1.211 or sipX.eltech.com (sipX FQDN) :

 

<<<<<<<<<<<<Incoming RawDataBuffer 172.18.1.200:5061<-172.18.1.210:4345

eINVITE sip:+3345 <at> mediation.esi.com:5061;user=phone;maddr=mediation.esi.com SIP/2.0

ms-user-data: ms-publiccloud=false;ms-federation=false

Record-Route: <sip:ocs.esi.com:5061;transport=tls;ms-role-rs-to;lr>;tag=E2C492B1BFDBD373E90670F181727F67

Via: SIP/2.0/TLS 172.18.1.210:4345;branch=z9hG4bKC4428C1B.04D62948;branched=TRUE

Max-Forwards: 69

Content-Length: 1071

Via: SIP/2.0/TLS 127.0.0.1:50071;received=172.18.0.205;ms-received-port=50072;ms-received-cid=4100

P-Asserted-Identity: "sinjo"<sip:sinjo <at> esi.com>,<tel:+2179751234>

From: "sinjo"<sip:sinjo <at> esi.com>;tag=b5b8cf48d8;epid=75094f81c7

To: <sip:+3345 <at> esi.com;user=phone>

Call-ID: 181afa82020049be9e8b430e2d924357

CSeq: 1 INVITE

Contact: <sip:sinjo <at> esi.com;opaque=user:epid:wLR4oI10klSGm5O0NMbKegAA;gruu>

User-Agent: UCCP/2.0.6362.64 OC/2.0.6362.64 (Microsoft Office Communicator)

Ms-Conversation-ID: Acj+yVOhS+hypfSFRuWyTv8Qmzq8OQ==

Supported: timer

Supported: ms-sender

Supported: ms-early-media

ms-keep-alive: UAC;hop-hop=yes

Supported: ms-conf-invite

Content-Type: application/sdp

 

 

 

 

 

2.       sipX to OCS. Below the debug captured on Mediation. Supposed the TO no to IP <at> is 172.18.1.211 because this is the IP <at> of sipX.

 

>>> Incoming TCP packet BEGIN

INVITE sip:2179751234 <at> 172.18.1.201:5060;transport=tcp SIP/2.0\r\n

Record-Route: <sip:172.18.1.211:5060;lr;sipXecs-rs=%2Afrom%7EMmEyOWFmNGY%60.400_authrules%2Aauth%7E%2162baf8ecf030d04ea30f350c1d357be1>\r\n

Max-Forwards: 16\r\n

Contact: <sip:3345 <at> 172.18.0.205:63498>\r\n

To: "02179751234"<sip:02179751234 <at> 172.18.1.211>\r\n

From: "Sinjo"<sip:3345 <at> 172.18.1.211>;tag=2a29af4f\r\n

Call-Id: OWQxNWMxZjgzNGRlNmQ3YzRhY2QzNzVkMDk3ZjEzNmY.\r\n

Cseq: 1 INVITE\r\n

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO\r\n

Content-Type: application/sdp\r\n

User-Agent: X-Lite release 1011s stamp 41150\r\n

Content-Length: 233\r\n

Date: Fri, 15 Aug 2008 11:22:27 GMT\r\n

Via: SIP/2.0/TCP 172.18.1.211;branch=z9hG4bK-sipXecs-000d219b4b79f93ba9f5705313e1de232fe3\r\n

Via: SIP/2.0/UDP 172.18.1.211;branch=z9hG4bK-sipXecs-000a2b88e2de789613c1a6057211d05d22dd~9bdd594f42281f01499ac7643eefdf5f\r\n

Via: SIP/2.0/UDP 172.18.1.211;branch=z9hG4bK-sipXecs-00059796ec64a36373cb15b04bf85d37e782~00f377e4a4073705fd337d222de50ac9\r\n

Via: SIP/2.0/UDP 172.18.0.205:63498;branch=z9hG4bK-d87543-ea5af023e70f7e29-1--d87543-;rport=63498\r\n

\r\n

 

 

Any one can help how to fix?

 

Tks.

Sinjo

<div>

<div class="Section1">

<p class="MsoNormal"><span lang="EN-US">Hello,<p></p></span></p>

<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoNormal"><span lang="EN-US">I am integrating OCS and sipX. I have a
problem which the calls both direction can not established/not ringing at both
end-point.<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US"><span>1.<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang="EN-US">OCS to sipX. When calling sipx
to OCS below the debug I capture on Mediation. Supposed TO is to sipX which the
IP <at>  172.18.1.211 or sipX.eltech.com (sipX FQDN) :<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;Incoming
RawDataBuffer 172.18.1.200:5061&lt;-172.18.1.210:4345<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">

eINVITE sip:+3345 <at> mediation.esi.com:5061;user=phone;maddr=mediation.esi.com
SIP/2.0<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">ms-user-data:
ms-publiccloud=false;ms-federation=false<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Record-Route:
&lt;sip:ocs.esi.com:5061;transport=tls;ms-role-rs-to;lr&gt;;tag=E2C492B1BFDBD373E90670F181727F67<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Via: SIP/2.0/TLS 172.18.1.210:4345;branch=z9hG4bKC4428C1B.04D62948;branched=TRUE<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Max-Forwards: 69<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Content-Length: 1071<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Via: SIP/2.0/TLS
127.0.0.1:50071;received=172.18.0.205;ms-received-port=50072;ms-received-cid=4100<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">P-Asserted-Identity:
"sinjo"&lt;sip:sinjo <at> esi.com&gt;,&lt;tel:+2179751234&gt;<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">From:
"sinjo"&lt;sip:sinjo <at> esi.com&gt;;tag=b5b8cf48d8;epid=75094f81c7<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">To:
&lt;sip:+3345 <at> esi.com;user=phone&gt;<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Call-ID:
181afa82020049be9e8b430e2d924357<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">CSeq: 1 INVITE<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Contact:
&lt;sip:sinjo <at> esi.com;opaque=user:epid:wLR4oI10klSGm5O0NMbKegAA;gruu&gt;<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">User-Agent: UCCP/2.0.6362.64
OC/2.0.6362.64 (Microsoft Office Communicator)<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Ms-Conversation-ID:
Acj+yVOhS+hypfSFRuWyTv8Qmzq8OQ==<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Supported: timer<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Supported: ms-sender<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Supported: ms-early-media<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">ms-keep-alive: UAC;hop-hop=yes<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Supported: ms-conf-invite<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Content-Type: application/sdp<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoListParagraph"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoListParagraph"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoListParagraph"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoListParagraph"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoListParagraph"><span lang="EN-US"><span>2.<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang="EN-US">sipX to OCS. Below the debug
captured on Mediation. Supposed the TO no to IP <at>  is 172.18.1.211 because this
is the IP <at>  of sipX.<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">&gt;&gt;&gt; Incoming TCP packet
BEGIN<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">INVITE
sip:2179751234 <at> 172.18.1.201:5060;transport=tcp SIP/2.0\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Record-Route:
&lt;sip:172.18.1.211:5060;lr;sipXecs-rs=%2Afrom%7EMmEyOWFmNGY%60.400_authrules%2Aauth%7E%2162baf8ecf030d04ea30f350c1d357be1&gt;\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Max-Forwards: 16\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Contact:
&lt;sip:3345 <at> 172.18.0.205:63498&gt;\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">To:
"02179751234"&lt;sip:02179751234 <at> 172.18.1.211&gt;\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">From:
"Sinjo"&lt;sip:3345 <at> 172.18.1.211&gt;;tag=2a29af4f\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Call-Id:
OWQxNWMxZjgzNGRlNmQ3YzRhY2QzNzVkMDk3ZjEzNmY.\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Cseq: 1 INVITE\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Allow: INVITE, ACK, CANCEL, OPTIONS,
BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Content-Type: application/sdp\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">User-Agent: X-Lite release 1011s
stamp 41150\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Content-Length: 233\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Date: Fri, 15 Aug 2008 11:22:27
GMT\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Via: SIP/2.0/TCP 172.18.1.211;branch=z9hG4bK-sipXecs-000d219b4b79f93ba9f5705313e1de232fe3\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Via: SIP/2.0/UDP
172.18.1.211;branch=z9hG4bK-sipXecs-000a2b88e2de789613c1a6057211d05d22dd~9bdd594f42281f01499ac7643eefdf5f\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Via: SIP/2.0/UDP
172.18.1.211;branch=z9hG4bK-sipXecs-00059796ec64a36373cb15b04bf85d37e782~00f377e4a4073705fd337d222de50ac9\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">Via: SIP/2.0/UDP
172.18.0.205:63498;branch=z9hG4bK-d87543-ea5af023e70f7e29-1--d87543-;rport=63498\r\n<p></p></span></p>

<p class="MsoListParagraph"><span lang="EN-US">\r\n<p></p></span></p>

<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoNormal"><span lang="EN-US">Any one can help how to fix?<p></p></span></p>

<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>

<p class="MsoNormal"><span lang="EN-US">Tks.<p></p></span></p>

<p class="MsoNormal"><span lang="EN-US">Sinjo<p></p></span></p>

</div>

</div>
Dale Worley | 18 Aug 18:21

Re: OCS-sipX

On Mon, 2008-08-18 at 11:39 +0700, Sinjo S Barakati wrote:
> Any one can help how to fix?

Try capturing a sipx-trace of the call and displaying it with sipviewer.
Start with 
http://sipx-wiki.calivia.com/index.php/Display_SIP_message_flow_using_Sipviewer

Dale


Gmane