In my opinion it is not correct. So the remote party sends me 400 Bad 
Content-lenth in response to my outgoing INVITE. That's why I'm asking this 
question. How to make this header only one. And why does opensips do this?
  
>Пятница, 8 ноября 2019, 11:14 +03:00 от [email protected]:
> 
>Send Users mailing list submissions to
>[email protected]
>
>To subscribe or unsubscribe via the World Wide Web, visit
>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>or, via email, send a message with subject or body 'help' to
>[email protected]
>
>You can reach the person managing the list at
>[email protected]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Users digest..."
>
>
>Today's Topics:
>
>   1. Opensips generate two Content-lenth headers (Oleg Podguyko)
>   2. Re: Opensips generate two Content-lenth headers (Alain Bieuzent)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Thu, 07 Nov 2019 21:15:10 +0300
>From: Oleg Podguyko < [email protected] >
>To:  [email protected]
>Subject: [OpenSIPS-Users] Opensips generate two Content-lenth headers
>Message-ID: < [email protected] >
>Content-Type: text/plain; charset="utf-8"
>
>
>I’m using opensips as proxy. I got INVITE from one side, do some logics 
>,remove ISUP body and send INVITE to destination via dispatcher module.
>And I see that outgoing INVITE has two content-lenth headers. Remote side 
>after received such INVITE sends 400 
>Bad Contenth-lenth header.
> 
> 
> 
>Incoming INVITE:
> 
>INVITE sip:[email protected];transport=sctp;user=phone SIP/2.0
>Via: SIP/2.0/SCTP 
>10.111.18.3:7010;branch=z9hG4bKiz5cvz9x5v5zi4bg84g4vx4zs;X-DispMsg=1408
>Route: <sip:10.66.107.169:5060;transport=sctp;lr>
>Call-ID:  [email protected]
>From: 
>"9269918424"<sip:[email protected];transport=sctp;user=phone>;tag=i4z5545v-CC-1027-TRC-613805-OFC-14
>To: "9222992040"<sip:[email protected];transport=sctp;user=phone>
>CSeq: 1 INVITE
>P-Access-Network-Info: GEN-ACCESS;"area-number= +79262000601 "
>Max-Forwards: 70
>Contact: <sip:10.111.18.3:7010>
>Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
>P-Asserted-Identity: <tel:9269918424>
>History-Info: 
><sip:[email protected]?reason=SIP%3Bcause%3D503%3Btext%3D%22Subscriber%20Not%20Reachable%22&Privacy=history>;index=1
>History-Info: <sip:[email protected]:5060;transport=sctp>;index=1.1
>P-Early-Media: supported
>Supported: 100rel,timer,histinfo
>Min-SE: 90
>Session-Expires: 1800;refresher=uac
>Content-Length: 477
>Content-Type: multipart/mixed;boundary=ssboundary
>--ssboundary
>Content-Length: 205
>Content-Type: application/sdp
>v=0
>o=xyz 1154444372 1154444373 IN IP4 10.111.18.3
>s=SipCall
>c=IN IP4 10.249.66.133
>t=0 0
>m=audio 28644 RTP/AVP 8 116
>a=rtpmap:8 PCMA/8000
>a=rtpmap:116 telephone-event/8000
>a=ptime:20
>--ssboundary
>Content-Length: 100
>Content-Type: application/isup;version=itu-t92+
> 
>)"
>)HB()EdRx1Z)EdRxa4}à§=?bñ£9
>1À4À?ÀoÀuÀ
>--ssboundary--
> 
> 
>Outgoing INVITE
> 
>INVITE sip:[email protected];transport=sctp;user=phone SIP/2.0
>Record-Route: <sip:192.168.9.84;r2=on;lr;did=876.0b9c196>
>Record-Route: <sip:10.66.107.169;transport=sctp;r2=on;lr;did=876.0b9c196>
>Via: SIP/2.0/UDP 192.168.9.84:5060;branch=z9hG4bKfa6a.b4f80a51.0
>Via: SIP/2.0/SCTP 
>10.111.18.3:7010;branch=z9hG4bKiz5cvz9x5v5zi4bg84g4vx4zs;X-DispMsg=1408
>Call-ID:  [email protected]
>From: 
>"9269918424"<sip:[email protected];transport=sctp;user=phone>;tag=i4z5545v-CC-1027-TRC-613805-OFC-14
>To: "9222992040"<sip:[email protected];transport=sctp;user=phone>
>CSeq: 1 INVITE
>P-Access-Network-Info: GEN-ACCESS;"area-number= +79262000601 "
>Max-Forwards: 69
>Contact: <sip:10.111.18.3:7010>
>Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
>P-Asserted-Identity: <tel:9269918424>
>History-Info: 
><sip:[email protected]?reason=SIP%3Bcause%3D503%3Btext%3D%22Subscriber%20Not%20Reachable%22&Privacy=history>;index=1
>History-Info: <sip:[email protected]:5060;transport=sctp>;index=1.1
>P-Early-Media: supported
>Supported: 100rel,timer,histinfo
>Min-SE: 90
>Session-Expires: 1800;refresher=uac
>Content-Length: 205
>Content-Length: 205
>Content-Type: application/sdp
>v=0
>o=xyz 1154444372 1154444373 IN IP4 10.111.18.3
>s=SipCall
>c=IN IP4 10.249.66.133
>t=0 0
>m=audio 28644 RTP/AVP 8 116
>a=rtpmap:8 PCMA/8000
>a=rtpmap:116 telephone-event/8000
>a=ptime:20
> 
> 
> 
> 
> 
>--
>Oleg Podguyko
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: < 
>http://lists.opensips.org/pipermail/users/attachments/20191107/99140cb6/attachment-0001.html
> >
>
>------------------------------
>
>Message: 2
>Date: Fri, 08 Nov 2019 09:13:43 +0100
>From: Alain Bieuzent < [email protected] >
>To: Oleg Podguyko < [email protected] >, OpenSIPS users mailling list
>< [email protected] >
>Subject: Re: [OpenSIPS-Users] Opensips generate two Content-lenth
>headers
>Message-ID: < [email protected] >
>Content-Type: text/plain; charset="utf-8"
>
>Hi Oleg,
>
> 
>
>Is it normal your outgoing INVITE have twice « Content-Length: 205 » ?
>
> 
>
>Regards
>
> 
>
>De : Users < [email protected] > au nom de Oleg Podguyko via 
>Users < [email protected] >
>Répondre à : Oleg Podguyko < [email protected] >, OpenSIPS users mailling list 
>< [email protected] >
>Date : jeudi 7 novembre 2019 à 19:16
>À : < [email protected] >
>Objet : [OpenSIPS-Users] Opensips generate two Content-lenth headers
>
> 
>
>I’m using opensips as proxy. I got INVITE from one side, do some logics 
>,remove ISUP body and send INVITE to destination via dispatcher module.
>
>And I see that outgoing INVITE has two content-lenth headers. Remote side 
>after received such INVITE sends 400
>
>Bad Contenth-lenth header.
>
> 
>
> 
>
> 
>
>Incoming INVITE:
>
> 
>
>INVITE sip:[email protected];transport=sctp;user=phone SIP/2.0
>Via: SIP/2.0/SCTP 
>10.111.18.3:7010;branch=z9hG4bKiz5cvz9x5v5zi4bg84g4vx4zs;X-DispMsg=1408
>Route: <sip:10.66.107.169:5060;transport=sctp;lr>
>Call-ID:  [email protected]
>From: 
>"9269918424"<sip:[email protected];transport=sctp;user=phone>;tag=i4z5545v-CC-1027-TRC-613805-OFC-14
>To: "9222992040"<sip:[email protected];transport=sctp;user=phone>
>CSeq: 1 INVITE
>P-Access-Network-Info: GEN-ACCESS;"area-number= +79262000601 "
>Max-Forwards: 70
>Contact: <sip:10.111.18.3:7010>
>Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
>P-Asserted-Identity: <tel:9269918424>
>History-Info: 
><sip:[email protected]?reason=SIP%3Bcause%3D503%3Btext%3D%22Subscriber%20Not%20Reachable%22&Privacy=history>;index=1
>History-Info: <sip:[email protected]:5060;transport=sctp>;index=1.1
>P-Early-Media: supported
>Supported: 100rel,timer,histinfo
>Min-SE: 90
>Session-Expires: 1800;refresher=uac
>Content-Length: 477
>Content-Type: multipart/mixed;boundary=ssboundary
>
>--ssboundary
>Content-Length: 205
>Content-Type: application/sdp
>
>v=0
>o=xyz 1154444372 1154444373 IN IP4 10.111.18.3
>s=SipCall
>c=IN IP4 10.249.66.133
>t=0 0
>m=audio 28644 RTP/AVP 8 116
>a=rtpmap:8 PCMA/8000
>a=rtpmap:116 telephone-event/8000
>a=ptime:20
>
>--ssboundary
>Content-Length: 100
>Content-Type: application/isup;version=itu-t92+
>
> 
>
>)"
>)HB()EdRx1Z
>)EdRxa4}à§=?bñ£9
>1À4À?ÀoÀuÀ
>--ssboundary--
>
> 
>
> 
>
>Outgoing INVITE
>
> 
>
>INVITE sip:[email protected];transport=sctp;user=phone SIP/2.0
>Record-Route: <sip:192.168.9.84;r2=on;lr;did=876.0b9c196>
>Record-Route: <sip:10.66.107.169;transport=sctp;r2=on;lr;did=876.0b9c196>
>Via: SIP/2.0/UDP 192.168.9.84:5060;branch=z9hG4bKfa6a.b4f80a51.0
>Via: SIP/2.0/SCTP 
>10.111.18.3:7010;branch=z9hG4bKiz5cvz9x5v5zi4bg84g4vx4zs;X-DispMsg=1408
>Call-ID:  [email protected]
>From: 
>"9269918424"<sip:[email protected];transport=sctp;user=phone>;tag=i4z5545v-CC-1027-TRC-613805-OFC-14
>To: "9222992040"<sip:[email protected];transport=sctp;user=phone>
>CSeq: 1 INVITE
>P-Access-Network-Info: GEN-ACCESS;"area-number= +79262000601 "
>Max-Forwards: 69
>Contact: <sip:10.111.18.3:7010>
>Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
>P-Asserted-Identity: <tel:9269918424>
>History-Info: 
><sip:[email protected]?reason=SIP%3Bcause%3D503%3Btext%3D%22Subscriber%20Not%20Reachable%22&Privacy=history>;index=1
>History-Info: <sip:[email protected]:5060;transport=sctp>;index=1.1
>P-Early-Media: supported
>Supported: 100rel,timer,histinfo
>Min-SE: 90
>Session-Expires: 1800;refresher=uac
>Content-Length: 205
>Content-Length: 205
>Content-Type: application/sdp
>v=0
>o=xyz 1154444372 1154444373 IN IP4 10.111.18.3
>s=SipCall
>c=IN IP4 10.249.66.133
>t=0 0
>m=audio 28644 RTP/AVP 8 116
>a=rtpmap:8 PCMA/8000
>a=rtpmap:116 telephone-event/8000
>a=ptime:20
> 
>
> 
>
> 
>
> 
>
> 
>
>--
>Oleg Podguyko
>
>_______________________________________________ Users mailing list  
>[email protected] 
>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: < 
>http://lists.opensips.org/pipermail/users/attachments/20191108/c6dfac88/attachment.html
> >
>
>------------------------------
>
>Subject: Digest Footer
>
>_______________________________________________
>Users mailing list
>[email protected]
>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>------------------------------
>
>End of Users Digest, Vol 136, Issue 11
>************************************** 
 
 
--
Олег Подгуйко
 
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to