Hi Jan,
First check the syslog for more info on the error. OpenSER generated an
internal error because it was not able to send out the BYE request (7
err code means no available socket).
Regards,
Bogdan
Jan P wrote:
Hi,
I made a pretty basic openser config with Sipwise but Im having problems
when sending BYE to my upstream SIP provider. When I do a CANCEL it
works but sending BYE the server doesnt forward any packets. Here's a
ngrep of whats happening. My complete openser.cfg can be found at
http://port53.se/openser.txt
#
U 99.88.164.203:30824 -> 101.12.20.26:5060
BYE sip:0709955324@bbr-ssw.sto.la.aa.net SIP/2.0.
Via: SIP/2.0/UDP
10.45.0.98:30824;branch=z9hG4bK-d87543-f13c745a11112e7c-1--d87543-;rport.
Max-Forwards: 70.
Route: <sip:101.12.20.26;lr;ftag=9a47eb12;nat=yes>.
Route: <sip:sipgw.sds.se;lr>.
Contact: <sip:0722465930@99.88.164.203:30824>.
To: "0709955324"<sip:0709955324@proxy.realm.se>;tag=ecbc244f.
From: "0722465930"<sip:0722465930@proxy.realm.se>;tag=9a47eb12.
Call-ID: ZDYwNjNjMmYzMTdiZGE3NTc4Nzc4OTA2NjdkOTllYTU..
CSeq: 3 BYE.
Proxy-Authorization: Digest
username="30000",realm="proxy.realm.se",nonce="487473f9db3e3da3ae9c3115a6d87d2023cc6b0a",uri="sip:0709955324@bbr-ssw.sto.la.aa.net",response="d9dc90e88deba0d9ba428bc11554b193",algorithm=MD5.
User-Agent: X-Lite release 1011s stamp 41150.
Reason: SIP;description="User Hung Up".
Content-Length: 0.
.
#
U 101.12.20.26:5060 -> 99.88.164.203:30824
SIP/2.0 500 I'm terribly sorry, server error occurred (7/TM).
Via: SIP/2.0/UDP
10.45.0.98:30824;branch=z9hG4bK-d87543-f13c745a11112e7c-1--d87543-;rport=30824;received=99.88.164.203.
To: "0709955324"<sip:0709955324@proxy3.digisip.net>;tag=ecbc244f.
From: "0722465930"<sip:0722465930@proxy3.digisip.net>;tag=9a47eb12.
Call-ID: ZDYwNjNjMmYzMTdiZGE3NTc4Nzc4OTA2NjdkOTllYTU..
CSeq: 3 BYE.
Server: OpenSer (1.1.0-notls (i386/linux)).
Content-Length: 0.
.
#
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users