Daniel-Constantin Mierla wrote:
On 09/28/05 11:00, Taymour A. El Erian wrote:
Daniel-Constantin Mierla wrote:
On 09/11/05 14:39, Taymour A. El Erian wrote:
[...]
I used the config u sent me now am getting this error in my log.
am using SEMS 0.9.0 and I have no idea what these errors mean
Sep 11 14:33:30 serry /usr/sbin/openser[20658]: ERROR: fifo_t_reply:
lookup failed
Sep 11 14:33:30 serry /usr/sbin/openser[20658]: ERROR: fifo_server:
command (t_reply) processing failed
Sep 11 14:33:30 serry Sems[19839]: Error: (AmRequest.cpp)(reply)(368):
AmRequestUAS::reply: 481 fifo_t_reply: no such transaction
Sep 11 14:33:30 serry Sems[19839]: Error:
(AmSession.cpp)(run)(217): 500
could not send response.
Did you get around this problem? The log messages say that sems tries
to send a reply to a transaction that does not exists in openser. This
can be due late reply (the transaction expired) bad parameters sent
over fifo from sems to openser.
Would help a network trace for such situation (using ngrep or
ethereal). Also, you can increase the debug level in openser and sems,
to get more messages.
Daniel
I did not get around it, It is definitely not a network problem since
sems and openser are on the same machine
The network trace of the SIP messages would help to figure out the
message flow and, maybe, to get the reason why the transaction is no
longer active. If you have openser and sems on same system then you
should watch the loopback interface, too:
ngrep -d lo port 5060
Daniel
>
>
>>> Sep 11 14:33:30 serry /usr/sbin/openser[20658]: ERROR: fifo_t_reply:
>>> lookup failed
>>> Sep 11 14:33:30 serry /usr/sbin/openser[20658]: ERROR: fifo_server:
>>> command (t_reply) processing failed
>>> Sep 11 14:33:30 serry Sems[19839]: Error: (AmRequest.cpp)(reply)(368):
>>> AmRequestUAS::reply: 481 fifo_t_reply: no such transaction
>>> Sep 11 14:33:33 serry /usr/sbin/openser[20666]: LOG: Someone trying to
>>> register from private IP, rewriting
>>> Sep 11 14:33:35 serry /usr/sbin/openser[20678]: LOG: Someone trying to
>>> register from private IP, rewriting
>>> Sep 11 14:33:35 serry /usr/sbin/openser[20624]: WARNING: t_reply: ACKs
>>> are not replied
>>>
>>>
>>>
>>
This is what I got from ngrep and I can't decrypt it :)
U IP:5060 -> IP:5090
INVITE sip:4000@IP:5090;user=phone SIP/2.0..Record-Route: <sip
:IP;ftag=c793260e386ee639;lr=on>..Via: SIP/2.0/UDP 212.103.160
.198;branch=z9hG4bKaf6b.be857c25.0..Via: SIP/2.0/UDP
10.99.4.2;rport=2474;r
eceived=212.103.165.18;branch=z9hG4bKe9a96c235da61c20..From: "Taymour
A. El
Erian" <sip:1101@tedata.net;user=phone>;tag=c793260e386ee639..To:
<sip:400
0@tedata.net;user=phone>..Contact:
<sip:1101@212.103.165.18:2474;user=phone
..Proxy-Authorization: DIGEST
username="1101", realm="tedata.net",
algorit
hm=MD5, uri="sip:4000@tedata.net;user=phone",
nonce="433b9e156151c6fff850be
0d40656ab14853786f",
response="097488dc945c51fdea29ce3dde36df28"..Call-ID:
07f54cd444bc0a36@10.99.4.2..CSeq: 63492 INVITE..User-Agent:
Grandstream BT1
00 1.0.5.10..Max-Forwards: 16..Allow:
INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OP
TIONS,INFO,SUBSCRIBE..Content-Type: application/sdp..Content-Length:
305...
.v=0..o=1101 8000 8000 IN IP4 10.99.4.2..s=SIP Call..c=IN IP4
10.99.4.2..t=
0 0..m=audio 5004 RTP/AVP 18 99 4 2 15 9..a=rtpmap:18
G729/8000..a=rtpmap:9
9 iLBC/8000..a=fmtp:99 mode=20..a=rtpmap:4 G723/8000..a=rtpmap:2
G726-32/80
00..a=rtpmap:15 G728/8000..a=rtpmap:9
G722/8000..a=ptime:20..a=direction:ac
tive..
#
U IP:5090 -> IP:5060
SIP/2.0 100 Trying -- just wait a minute !..Via: SIP/2.0/UDP
212.103.160.19
8;branch=z9hG4bKaf6b.be857c25.0..Via: SIP/2.0/UDP
10.99.4.2;rport=2474;rece
ived=212.103.165.18;branch=z9hG4bKe9a96c235da61c20..From: "Taymour A.
El Er
ian" <sip:1101@tedata.net;user=phone>;tag=c793260e386ee639..To:
<sip:4000@t
edata.net;user=phone>..Call-ID: 07f54cd444bc0a36@10.99.4.2..CSeq:
63492 INV
ITE..Server: OpenSer (0.9.5 (i386/linux))..Content-Length: 0..Warning: 392
IP:5090 "Noisy feedback tells: pid=821 req_src_ip=212.103.160
.198 req_src_port=5060 in_uri=sip:4000@IP:5090;user=phone out_
uri=sip:4000@IP:5090;user=phone via_cnt==2"....
#
U IP:5060 -> IP:5090
CANCEL sip:4000@IP:5090;user=phone SIP/2.0..Via: SIP/2.0/UDP 2
12.103.160.198;branch=z9hG4bKaf6b.be857c25.0..From: "Taymour A. El
Erian" <
sip:1101@tedata.net;user=phone>;tag=c793260e386ee639..Call-ID:
07f54cd444bc
0a36@10.99.4.2..To: <sip:4000@tedata.net;user=phone>..CSeq: 63492
CANCEL..U
ser-Agent: OpenSer (0.9.5 (i386/linux))..Content-Length: 0....
#
U IP:5090 -> IP:5060
SIP/2.0 200 cancels are junked here..Via: SIP/2.0/UDP IP;branc
h=z9hG4bKaf6b.be857c25.0..From: "Taymour A. El Erian"
<sip:1101@tedata.net;
user=phone>;tag=c793260e386ee639..Call-ID: 07f54cd444bc0a36@10.99.4.2..To:
<sip:4000@tedata.net;user=phone>;tag=295de06b31c02f814974318d00ff602d.3f4c.
.CSeq: 63492 CANCEL..Server: OpenSer (0.9.5 (i386/linux))..Content-Length:
0..Warning: 392 IP:5090 "Noisy feedback tells: pid=823 req_sr
c_ip=IP req_src_port=5060 in_uri=sip:4000@IP:5090
;user=phone out_uri=sip:4000@IP:5090;user=phone via_cnt==1"..
--
Taymour A El Erian
System Division Manager
RHCE, LPIC, CCNA, MCSE, CNA
TE Data
E-mail: taymour.elerian(a)tedata.net
Web:
www.tedata.net
Tel: +(202)-4166600
Fax: +(202)-4166700
Ext: 1101