[OpenSIPS-Users] 500 Server Internal Error
Arjun Shankar K S
arjun_ks at kalycito.com
Mon Jul 16 10:58:34 CEST 2012
Hi Bogdan,
I meant the Codec number in the Payload Type(PT) of the SDP header for call initiation.
Thanks,
Arjun
----- Original Message -----
From: "Bogdan-Andrei Iancu" <bogdan at opensips.org>
To: "Arjun Shankar K S" <arjun_ks at kalycito.com>
Cc: "OpenSIPS users mailling list" <users at lists.opensips.org>
Sent: Monday, July 16, 2012 2:25:54 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi
Subject: Re: [OpenSIPS-Users] 500 Server Internal Error
RTPproxy is not codec aware (codecs are totally transparent for rtpproxy). And even if it is a code problem, a UAC SHOULD NOT generate ANY reply for an ACK.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
On 07/16/2012 11:52 AM, Arjun Shankar K S wrote:
Hi Bogdan,
Thanks Bogdan. My UAC supports only AMR codec and as I understand that RTP Proxy does not support it. Can this be the issue?
Thanks,
Arjun
----- Original Message -----
From: "Bogdan-Andrei Iancu" <bogdan at opensips.org>
To: "Arjun Shankar K S" <arjun_ks at kalycito.com>
Cc: "OpenSIPS users mailling list" <users at lists.opensips.org>
Sent: Monday, July 16, 2012 2:07:23 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi
Subject: Re: [OpenSIPS-Users] 500 Server Internal Error
Hi ARjun,
Well, the 500 reply is generated by one of your UACs (why? check with the UAC) - what is really brain dead is that the reply is for an ACK requests (see the cseq hdr in reply) - and according to SIP RFC3261, ACK requests do not have replies at all!
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
On 07/16/2012 09:41 AM, Arjun Shankar K S wrote:
Hi Bogdan,
The opensips server is running in a 220.225.134.9 public IP. All UACs are in the 220.225.134.x series. The SIP Trace is as given below,
|Time | 220.225.134.9 |
| | | 10.100.4.64 |
|11.678 | INVITE SDP (AMRRTPType-114) |SIP From: < sip:1016@ 220.225.134.9 To:< sip:1012@ 220.225.134.9
| |(5060) ------------------> (5060) |
|12.182 | INVITE SDP (AMRRTPType-114) |SIP From: < sip:1016@ 220.225.134.9 To:< sip:1012@ 220.225.134.9
| |(5060) ------------------> (5060) |
|12.899 | 100 Trying| |SIP Status
| |(5060) <------------------ (5060) |
|13.209 | 180 Ringing |SIP Status
| |(5060) <------------------ (5060) |
|21.007 | 200 OK SDP (AMRRTPType-114) |SIP Status
| |(5060) <------------------ (5060) |
|21.126 | ACK | |SIP Request
| |(5060) ------------------> (5060) |
|21.579 | 200 OK SDP (AMRRTPType-114) |SIP Status
| |(5060) <------------------ (5060) |
|22.186 | 500 Server Internal Error |SIP Status
| |(5060) <------------------ (5060) |
And the ngrep capture was as I had put in my previous mail.
Thanks,
Arjun
----- Original Message -----
From: "Bogdan-Andrei Iancu" <bogdan at opensips.org>
To: "Arjun Shankar K S" <arjun_ks at kalycito.com>
Cc: "OpenSIPS users mailling list" <users at lists.opensips.org>
Sent: Friday, July 13, 2012 6:40:34 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi
Subject: Re: [OpenSIPS-Users] 500 Server Internal Error
Arjun,
That is really foobar.....What device is 220.225.134.2:13120 and why is it generating a reply for an ACK request !?!?! ACK HAVE NOT replies at all :)
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
On 07/13/2012 01:52 PM, Arjun Shankar K S wrote:
Hi Bogdan,
Please find below the ngrep capture at the SIP server side,
##################################################################################################################################################################################################################################################################################
U(17) 220.225.134.2:13120 -> 220.225.134.9:5060
SIP/2.0 200 OK..Record-Route: <sip:220.225.134.9;lr=on> ..Call-Id: 58f64298f3186a42b96a608659fd434d at 220.225.134.9..CSeq: 1 INVITE..To: <sip:1005 at 220.225.134.9> ;tag
=4IHoLZ2ha..Via: SIP/2.0/UDP 220.225.134.9:5060;branch=z9hG4bKec6a.856da06.0,SIP/2.0/UDP 220.225.134.9:5060;received=203.199.234.3;rport=41792;branch=z9hG4bKd8feb
fe85d601ca1b48d8bd8e6a10ba6..From: <sip:1012 at 220.225.134.9> ;tag=LXMkFpqUA..Contact: <sip:220.225.134.9:5060> ..Content-Type: application/sdp..Content-Length: 197..
..v=0..o=blackberry 1342175741968 1342175741968 IN IP4 220.225.134.2..s=Phone call..c=IN IP4 220.225.134.2..t=0 0..t=0 0..m=audio 7078 RTP/AVP 114..a=rtpmap:114 A
MR/8000/1..a=fmtp:114 octet-align=1..
#
U(17) 220.225.134.9:5060 -> 203.199.234.3:41792
SIP/2.0 200 OK..Record-Route: <sip:220.225.134.9;lr=on> ..Call-Id: 58f64298f3186a42b96a608659fd434d at 220.225.134.9..CSeq: 1 INVITE..To: <sip:1005 at 220.225.134.9> ;tag
=4IHoLZ2ha..Via: SIP/2.0/UDP 220.225.134.9:5060;received=203.199.234.3;rport=41792;branch=z9hG4bKd8febfe85d601ca1b48d8bd8e6a10ba6..From: <sip:1012 at 220.225.134.9> ;
tag=LXMkFpqUA..Contact: <sip:220.225.134.2:13120;nat=yes> ..Content-Type: application/sdp..Content-Length: 216..P-hint: onreply_route|force_rtp_proxy ..P-hint: Onr
eply-route - fixcontact ....v=0..o=blackberry 1342175741968 1342175741968 IN IP4 220.225.134.2..s=Phone call..c=IN IP4 220.225.134.9..t=0 0..t=0 0..m=audio 38476
RTP/AVP 114..a=rtpmap:114 AMR/8000/1..a=fmtp:114 octet-align=1..a=nortpproxy:yes..
#############################
U(17) 203.199.234.3:41792 -> 220.225.134.9:5060
ACK sip:220.225.134.2:13120;nat=yes SIP/2.0..Call-Id: 58f64298f3186a42b96a608659fd434d at 220.225.134.9..CSeq: 1 ACK..To: <sip:1005 at 220.225.134.9> ;tag=4IHoLZ2ha..Via
: SIP/2.0/UDP 220.225.134.9:5060;rport;branch=z9hG4bK202da30a90a53ad5d81d9256e09b6db6..Max-Forwards: 70..From: <sip:1012 at 220.225.134.9> ;tag=LXMkFpqUA..Contact: <s
ip:1012 at 203.199.234.3:41792 >..Route: <sip:220.225.134.9;lr=on> ..Content-Length: 0....
#
U(17) 220.225.134.9:5060 -> 220.225.134.2:13120
ACK sip:220.225.134.2:13120 SIP/2.0..Call-Id: 58f64298f3186a42b96a608659fd434d at 220.225.134.9..CSeq: 1 ACK..To: <sip:1005 at 220.225.134.9> ;tag=4IHoLZ2ha..Via: SIP/2.
0/UDP 220.225.134.9;branch=z9hG4bKec6a.856da06.2..Via: SIP/2.0/UDP 220.225.134.9:5060;received=203.199.234.3;rport=41792;branch=z9hG4bK202da30a90a53ad5d81d9256e09
b6db6..Max-Forwards: 69..From: <sip:1012 at 220.225.134.9> ;tag=LXMkFpqUA..Contact: <sip:1012 at 203.199.234.3:41792;nat=yes> ..Content-Length: 0....
################
U(17) 220.225.134.2:13120 -> 220.225.134.9:5060
SIP/2.0 200 OK..Record-Route: <sip:220.225.134.9;lr=on> ..Call-Id: 58f64298f3186a42b96a608659fd434d at 220.225.134.9..CSeq: 1 INVITE..To: <sip:1005 at 220.225.134.9> ;tag
=4IHoLZ2ha..Via: SIP/2.0/UDP 220.225.134.9:5060;branch=z9hG4bKec6a.856da06.0,SIP/2.0/UDP 220.225.134.9:5060;received=203.199.234.3;rport=41792;branch=z9hG4bKd8feb
fe85d601ca1b48d8bd8e6a10ba6..From: <sip:1012 at 220.225.134.9> ;tag=LXMkFpqUA..Contact: <sip:220.225.134.9:5060> ..Content-Type: application/sdp..Content-Length: 197..
..v=0..o=blackberry 1342175741968 1342175741968 IN IP4 220.225.134.2..s=Phone call..c=IN IP4 220.225.134.2..t=0 0..t=0 0..m=audio 7078 RTP/AVP 114..a=rtpmap:114 A
MR/8000/1..a=fmtp:114 octet-align=1..
#
U(17) 220.225.134.9:5060 -> 203.199.234.3:41792
SIP/2.0 200 OK..Record-Route: <sip:220.225.134.9;lr=on> ..Call-Id: 58f64298f3186a42b96a608659fd434d at 220.225.134.9..CSeq: 1 INVITE..To: <sip:1005 at 220.225.134.9> ;tag
=4IHoLZ2ha..Via: SIP/2.0/UDP 220.225.134.9:5060;received=203.199.234.3;rport=41792;branch=z9hG4bKd8febfe85d601ca1b48d8bd8e6a10ba6..From: <sip:1012 at 220.225.134.9> ;
tag=LXMkFpqUA..Contact: <sip:220.225.134.2:13120;nat=yes> ..Content-Type: application/sdp..Content-Length: 216..P-hint: onreply_route|force_rtp_proxy ..P-hint: Onr
eply-route - fixcontact ....v=0..o=blackberry 1342175741968 1342175741968 IN IP4 220.225.134.2..s=Phone call..c=IN IP4 220.225.134.9..t=0 0..t=0 0..m=audio 38476
RTP/AVP 114..a=rtpmap:114 AMR/8000/1..a=fmtp:114 octet-align=1..a=nortpproxy:yes..
#################
U(17) 220.225.134.2:13120 -> 220.225.134.9:5060
SIP/2.0 500 Server Internal Error..Call-Id: 58f64298f3186a42b96a608659fd434d at 220.225.134.9..CSeq: 1 ACK..To: <sip:1005 at 220.225.134.9> ;tag=4IHoLZ2ha..Via: SIP/2.0/
UDP 220.225.134.9:5060;branch=z9hG4bKec6a.856da06.2,SIP/2.0/UDP 220.225.134.9:5060;received=203.199.234.3;rport=41792;branch=z9hG4bK202da30a90a53ad5d81d9256e09b6d
b6..From: <sip:1012 at 220.225.134.9> ;tag=LXMkFpqUA..Contact: <sip:220.225.134.9:5060> ..Content-Length: 0....
#######################################################################################################
U(17) 220.225.134.9:5060 -> 220.225.134.2:13120
OPTIONS sip:220.225.134.2:13120 SIP/2.0..Via: SIP/2.0/UDP 220.225.134.9:5060;branch=0..From: sip:pinger at PROXY_IP;tag=63cac2b..To: sip:220.225.134.2:13120..Call-ID
: 20233266-bc88a9d3-5342d at 220.225.134.9..CSeq: 1 OPTIONS..Content-Length: 0....
#####################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################
U(17) 220.225.134.9:5060 -> 203.199.234.3:24922
OPTIONS sip:203.199.234.3:24922 SIP/2.0..Via: SIP/2.0/UDP 220.225.134.9:5060;branch=0..From: sip:pinger at PROXY_IP;tag=73cac2b..To: sip:203.199.234.3:24922..Call-ID
: 20233266-cc88a9d3-9342d at 220.225.134.9..CSeq: 1 OPTIONS..Content-Length: 0....
##################################
U(17) 203.199.234.3:24922 -> 220.225.134.9:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 220.225.134.9:5060;branch=0..Contact: <sip:10.100.4.156:20958> ..To: <sip:203.199.234.3:24922> ;tag=190a3f50..From: < sip:pinger at PRO
XY_IP>;tag=73cac2b..Call-ID: 20233266-cc88a9d3-9342d at 220.225.134.9..CSeq: 1 OPTIONS..Accept: application/sdp..Accept-Language: en..Allow: INVITE, ACK, CANCEL, OPT
IONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..User-Agent: X-Lite release 1103k stamp 53621..Content-Length: 0....
#############################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################
U(17) 220.225.134.9:5060 -> 59.144.118.72:21788
OPTIONS sip:59.144.118.72:21788 SIP/2.0..Via: SIP/2.0/UDP 220.225.134.9:5060;branch=0..From: sip:pinger at PROXY_IP;tag=83cac2b..To: sip:59.144.118.72:21788..Call-ID
: 20233266-dc88a9d3-c342d at 220.225.134.9..CSeq: 1 OPTIONS..Content-Length: 0....
####################################
U(17) 59.144.118.72:21788 -> 220.225.134.9:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 220.225.134.9:5060;branch=0..Contact: <sip:192.168.1.112:21788> ..To: <sip:59.144.118.72:21788> ;tag=bc7b1d12..From: < sip:pinger at PR
OXY_IP>;tag=83cac2b..Call-ID: 20233266-dc88a9d3-c342d at 220.225.134.9..CSeq: 1 OPTIONS..Accept: application/sdp..Accept-Language: en..Allow: INVITE, ACK, CANCEL, OP
TIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..Supported: replaces..User-Agent: X-Lite 4 release 4.1 stamp 63215..Content-Length: 0....
#########################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################
U(17) 220.225.134.9:5060 -> 59.144.118.72:57246
OPTIONS sip:59.144.118.72:57246 SIP/2.0..Via: SIP/2.0/UDP 220.225.134.9:5060;branch=0..From: sip:pinger at PROXY_IP;tag=93cac2b..To: sip:59.144.118.72:57246..Call-ID
: 20233266-ec88a9d3-1442d at 220.225.134.9..CSeq: 1 OPTIONS..Content-Length: 0....
###############################
U(17) 59.144.118.72:57246 -> 220.225.134.9:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 220.225.134.9:5060;branch=0..From: <sip:pinger at PROXY> ;tag=61cac2b..To: <sip:59.144.118.72:57246> ;tag=1255356873..Contact: < sip:pi
nger at 59.144.118.72:57246;transport=udp >..Call-ID: 20233266-ba88a9d3-3242d at 220.225.134.9..CSeq: 1 OPTIONS..Content-Length: 0....
############################################################################################################################################
Please let me know where the error is.
Thanks,
Arjun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120716/9258549c/attachment-0001.htm>
More information about the Users
mailing list