[OpenSIPS-Users] how does OpenSIPS manage 183's message??

Tue Dec 13 17:12:36 CET 2011

Hi all, I am still testing my solution to provide some additional features to
own Fax server, thanks to OpenSIPS.

IP-PBX<----> OpenSIPS <----> Fax Server

I am using OpenSIPS in stateless mode ( so without record-route ) and this
is the sip trace at OpenSIPS level

U 2011/12/13 15:46:04.075195 172.16.52.7:5061 -> 10.9.101.166:5060
INVITE sip:0363394686180 at 10.9.101.166:5060;user=phone SIP/2.0.
Via: SIP/2.0/UDP 172.16.52.7:5061.
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
To: sip:0363394686180 at 10.9.101.166:5060.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Max-Forwards: 70.
Contact: <sip:+390522375507 at 172.16.52.7:5061;user=phone>.
User-Agent: Alcatel-Lucent OmniTouch Fax Server Application/6.5.6.28.
P-Alcatel-CSBU: charging=sip:2542 at ucalcatel.sedoc.locale.
Content-Type: application/sdp.
Content-Length: 211.
.
v=0.
o=XMedius-Fax-Gateway 55439616 616 IN IP4 172.16.52.7.
s=SIP Fax Call.
c=IN IP4 172.16.52.7.
t=0 0.
m=audio 46022 RTP/AVP 18 8.
a=rtpmap:18 G729/8000.
a=fmtp:18 annexb=no.
a=rtpmap:8 PCMA/8000.
a=ptime:20.

U 2011/12/13 15:46:04.080484 10.9.101.166:5060 -> 172.16.52.7:5061
SIP/2.0 100 Giving a try.
Via: SIP/2.0/UDP 172.16.52.7:5061.
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
To: sip:0363394686180 at 10.9.101.166:5060.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Server: OpenSIPS-Longwave.
Content-Length: 0.
.

U 2011/12/13 15:46:04.080927 10.9.101.166:5060 -> 10.9.6.3:5060
INVITE sip:87019363394686180 at 10.9.6.3:5060;user=phone SIP/2.0.
Via: SIP/2.0/UDP 10.9.101.166;branch=z9hG4bK8106.0a3d7b63.0.
Via: SIP/2.0/UDP 172.16.52.7:5061.
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
To: sip:87019363394686180 at 10.9.6.3:5060.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Max-Forwards: 69.
Contact: <sip:+390522375507 at 172.16.52.7:5061;user=phone>.
User-Agent: Alcatel-Lucent OmniTouch Fax Server Application/6.5.6.28.
P-Alcatel-CSBU: charging=sip:2542 at ucalcatel.sedoc.locale.
Content-Type: application/sdp.
Content-Length: 211.
.
v=0.
o=XMedius-Fax-Gateway 55439616 616 IN IP4 172.16.52.7.
s=SIP Fax Call.
c=IN IP4 172.16.52.7.
t=0 0.
m=audio 46022 RTP/AVP 18 8.
a=rtpmap:18 G729/8000.
a=fmtp:18 annexb=no.
a=rtpmap:8 PCMA/8000.
a=ptime:20.

U 2011/12/13 15:46:04.082838 10.9.6.3:5060 -> 10.9.101.166:5060
SIP/2.0 100 Trying.
To: sip:87019363394686180 at 10.9.6.3:5060.
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Via: SIP/2.0/UDP 10.9.101.166;branch=z9hG4bK8106.0a3d7b63.0.
Via: SIP/2.0/UDP 172.16.52.7:5061.
Content-Length: 0.
.

U 2011/12/13 15:46:04.506636 10.9.6.3:5060 -> 10.9.101.166:5060
SIP/2.0 183 Session Progress.
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS,
UPDATE.
Contact: sip:10.9.6.3.
User-Agent: OmniPCX Enterprise R9.0 h1.301.50.
P-Alcatel-CSBU: categparty=external.
Content-Type: application/sdp.
To:
sip:87019363394686180 at 10.9.6.3:5060;tag=3439ea69c02c4dd7146a60c535fa4a06.
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Via: SIP/2.0/UDP 10.9.101.166;branch=z9hG4bK8106.0a3d7b63.0.
Via: SIP/2.0/UDP 172.16.52.7:5061.
Content-Length: 229.
.
v=0.
o=OXE 1323791155 1323791155 IN IP4 10.9.6.3.
s=abs.
c=IN IP4 10.9.6.8.
t=0 0.
m=audio 32560 RTP/AVP 18 96.
a=rtpmap:18 G729/8000.
a=fmtp:18 annexb=no.
a=ptime:30.
a=maxptime:40.
a=rtpmap:96 telephone-event/8000.
a=sendrecv.

U 2011/12/13 15:46:04.508542 10.9.101.166:5060 -> 172.16.52.7:5061
SIP/2.0 183 Session Progress.
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS,
UPDATE.
Contact: sip:10.9.6.3.
User-Agent: OmniPCX Enterprise R9.0 h1.301.50.
P-Alcatel-CSBU: categparty=external.
Content-Type: application/sdp.
To:
sip:0363394686180 at 10.9.101.166:5060;tag=3439ea69c02c4dd7146a60c535fa4a06.
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Via: SIP/2.0/UDP 172.16.52.7:5061.
Content-Length: 229.
.
v=0.
o=OXE 1323791155 1323791155 IN IP4 10.9.6.3.
s=abs.
c=IN IP4 10.9.6.8.
t=0 0.
m=audio 32560 RTP/AVP 18 96.
a=rtpmap:18 G729/8000.
a=fmtp:18 annexb=no.
a=ptime:30.
a=maxptime:40.
a=rtpmap:96 telephone-event/8000.
a=sendrecv.

U 2011/12/13 15:46:06.028272 10.9.6.3:5060 -> 10.9.101.166:5060
SIP/2.0 180 Ringing.
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS,
UPDATE.
Contact: sip:10.9.6.3.
User-Agent: OmniPCX Enterprise R9.0 h1.301.50.
P-Alcatel-CSBU: categparty=external.
Content-Type: application/sdp.
To:
sip:87019363394686180 at 10.9.6.3:5060;tag=3439ea69c02c4dd7146a60c535fa4a06.
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Via: SIP/2.0/UDP 10.9.101.166;branch=z9hG4bK8106.0a3d7b63.0.
Via: SIP/2.0/UDP 172.16.52.7:5061.
Content-Length: 229.
.
v=0.
o=OXE 1323791155 1323791156 IN IP4 10.9.6.3.
s=abs.
c=IN IP4 10.9.6.8.
t=0 0.
m=audio 32560 RTP/AVP 18 96.
a=rtpmap:18 G729/8000.
a=fmtp:18 annexb=no.
a=ptime:30.
a=maxptime:40.
a=rtpmap:96 telephone-event/8000.
a=sendrecv.

U 2011/12/13 15:46:06.029873 10.9.101.166:5060 -> 172.16.52.7:5061
SIP/2.0 180 Ringing.
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS,
UPDATE.
Contact: sip:10.9.6.3.
User-Agent: OmniPCX Enterprise R9.0 h1.301.50.
P-Alcatel-CSBU: categparty=external.
Content-Type: application/sdp.
To:
sip:0363394686180 at 10.9.101.166:5060;tag=3439ea69c02c4dd7146a60c535fa4a06.
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Via: SIP/2.0/UDP 172.16.52.7:5061.
Content-Length: 229.
.
v=0.
o=OXE 1323791155 1323791156 IN IP4 10.9.6.3.
s=abs.
c=IN IP4 10.9.6.8.
t=0 0.
m=audio 32560 RTP/AVP 18 96.
a=rtpmap:18 G729/8000.
a=fmtp:18 annexb=no.
a=ptime:30.
a=maxptime:40.
a=rtpmap:96 telephone-event/8000.
a=sendrecv.

U 2011/12/13 15:46:06.030671 10.9.6.3:5060 -> 10.9.101.166:5060
SIP/2.0 200 OK.
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS,
UPDATE.
Contact: sip:10.9.6.3.
Supported: replaces,timer,100rel.
User-Agent: OmniPCX Enterprise R9.0 h1.301.50.
Session-Expires: 1800;refresher=uas.
P-Alcatel-CSBU: categparty=external.
P-Asserted-Identity: "Lw Re" <sip:10.9.6.3;user=phone>.
Content-Type: application/sdp.
To:
sip:87019363394686180 at 10.9.6.3:5060;tag=3439ea69c02c4dd7146a60c535fa4a06.
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Via: SIP/2.0/UDP 10.9.101.166;branch=z9hG4bK8106.0a3d7b63.0.
Via: SIP/2.0/UDP 172.16.52.7:5061.
Content-Length: 229.
.
v=0.
o=OXE 1323791155 1323791157 IN IP4 10.9.6.3.
s=abs.
c=IN IP4 10.9.6.8.
t=0 0.
m=audio 32560 RTP/AVP 18 96.
a=rtpmap:18 G729/8000.
a=fmtp:18 annexb=no.
a=ptime:30.
a=maxptime:40.
a=rtpmap:96 telephone-event/8000.
a=sendrecv.

U 2011/12/13 15:46:06.031402 10.9.101.166:5060 -> 172.16.52.7:5061
SIP/2.0 200 OK.
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS,
UPDATE.
Contact: sip:10.9.6.3.
Supported: replaces,timer,100rel.
User-Agent: OmniPCX Enterprise R9.0 h1.301.50.
Session-Expires: 1800;refresher=uas.
P-Alcatel-CSBU: categparty=external.
P-Asserted-Identity: "Lw Re" <sip:10.9.6.3;user=phone>.
Content-Type: application/sdp.
To:
sip:0363394686180 at 10.9.101.166:5060;tag=3439ea69c02c4dd7146a60c535fa4a06.
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Via: SIP/2.0/UDP 172.16.52.7:5061.
Content-Length: 229.
.
v=0.
o=OXE 1323791155 1323791157 IN IP4 10.9.6.3.
s=abs.
c=IN IP4 10.9.6.8.
t=0 0.
m=audio 32560 RTP/AVP 18 96.
a=rtpmap:18 G729/8000.
a=fmtp:18 annexb=no.
a=ptime:30.
a=maxptime:40.
a=rtpmap:96 telephone-event/8000.
a=sendrecv. 

As you can see, IP_PBX ( 10.9.6.3 ) reply to Fax Server ( via OpenSIPS )
with a 183 message and with TO header as aspected:

U 2011/12/13 15:46:04.506636 *10.9.6.3:5060 -> 10.9.101.166*:5060
SIP/2.0 183 Session Progress.
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS,
UPDATE.
Contact: sip:10.9.6.3.
User-Agent: OmniPCX Enterprise R9.0 h1.301.50.
P-Alcatel-CSBU: categparty=external.
Content-Type: application/sdp.
*To:
sip:87019363394686180 at 10.9.6.3:5060;tag=3439ea69c02c4dd7146a60c535fa4a06.*
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Via: SIP/2.0/UDP 10.9.101.166;branch=z9hG4bK8106.0a3d7b63.0.
Via: SIP/2.0/UDP 172.16.52.7:5061.
Content-Length: 229.

So, When OpenSIPS forward to Fax server the 183 message, it modify the TO
header like this:

U 2011/12/13 15:46:04.508542 *10.9.101.166:5060 -> 172.16.52.7:5061*
SIP/2.0 183 Session Progress.
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS,
UPDATE.
Contact: sip:10.9.6.3.
User-Agent: OmniPCX Enterprise R9.0 h1.301.50.
P-Alcatel-CSBU: categparty=external.
Content-Type: application/sdp.
*To:
sip:0363394686180 at 10.9.101.166:5060;tag=3439ea69c02c4dd7146a60c535fa4a06.*
From: Fax Alcatel <sip:+390522375507 at 172.16.52.7:5061>;tag=11D255FDC152.
Call-ID: 219ffbfb-58a0-41e1-acdc-82966f3a1f49 at 172.16.52.7.
CSeq: 101 INVITE.
Via: SIP/2.0/UDP 172.16.52.7:5061.
Content-Length: 229.

As you can see, TO header is modified

*To:
sip:0363394686180 at 10.9.101.166:5060;tag=3439ea69c02c4dd7146a60c535fa4a06.*

but I DON'T understand why. It should be like this:

*To:
sip:87019363394686180 at 10.9.6.3:5060;tag=3439ea69c02c4dd7146a60c535fa4a06.*

So, my question is, where in opensips.cfg it modify TO header? How Does
OpenSIPS manage it? I did not setup any part of script to handle it... Can
you explain how it works?

Thanks and best regards....

--
View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/how-does-OpenSIPS-manage-183-s-message-tp7090462p7090462.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.