Hi David,
OpenSIPS by itself does not generate such a reply, so:
1) either the reply comes from script
2) either reply is not gnerated by opensips, but by other entity on
the path
Regards,
Bogdan
On 07/06/2011 08:00 AM, David Cunningham wrote:
Hi all,
We're seeing a strange reply from OpenSIPS when Asterisk sends it a
BYE - "481 bad request, no route tag". Does anyone know why this
message might be returned? Thanks in advance.
U 2011/07/05 20:38:32.406967 <asterisk ip>:5060 -> <opensips ip>:5060
BYE sip:<calling number>@<opensips ip>:5060 SIP/2.0.
Record-Route: <sip:<asterisk ip>;lr=on;ftag=as0e8489a0>.
Via: SIP/2.0/UDP <asterisk ip>;branch=z9hG4bK75db.9be45641.0.
Via: SIP/2.0/UDP
216.139.220.96:5060;received=216.139.220.96;branch=z9hG4bK52a32816;rport=5060.
Route: <sip:<asterisk
ip>;lr=on;ftag=sansay303254289rdb21376>,<sip:sansay303254289rdb21376@<opensips
ip>:5060;lr;transport=udp>.
Max-Forwards: 69.
From: <sip:<called number>@<asterisk ip>>;tag=as0e8489a0.
To: <sip:<calling number>@<opensips ip>>;tag=sansay303254289rdb21376.
Call-ID: 109061978-0-425332974@<did provider ip>.
CSeq: 102 BYE.
User-Agent: Product.
X-Asterisk-HangupCause: Normal Clearing.
X-Asterisk-HangupCauseCode: 16.
Content-Length: 0.
X-Product-RURI: sip:<calling number>@<opensips ip>:5060.
X-Product-Source: 216.139.220.96:5060 <http://216.139.220.96:5060>.
.
U 2011/07/05 20:38:32.478093 <opensips ip>:5060 -> <asterisk ip>:5060
SIP/2.0 481 bad request, no route tag.
Via: SIP/2.0/UDP <asterisk ip>;branch=z9hG4bK75db.9be45641.0.
Via: SIP/2.0/UDP
216.139.220.96:5060;received=216.139.220.96;branch=z9hG4bK52a32816;rport=5060.
To: <sip:<calling number>@<opensips ip>>;tag=sansay303254289rdb21376.
From: <sip:<called number>@<asterisk ip>>;tag=as0e8489a0.
Call-ID: 109061978-0-425332974@<did provider ip>.
CSeq: 102 BYE.
Content-Length: 0.
.
--
Bogdan-Andrei Iancu
OpenSIPS solutions and "know-how"
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
