Hello,
I'm trying to figure out why sending a DTMF (SIP mode,
info-tone) is so
long...
To help, I've added some traces in the sippdu.cxx file, and
here they are :
Sending "1" to
1a1b269c-212d-db11-8988-0030484233fa ref-dev.def.com.com
0:21.235 SimpleOPAL sipcon.cxx(2678) SIP
SendUserInputTime('1', 0), using mode SendUserInputAsTone
0:21.238 SimpleOPAL sipcon.cxx(2696) SIP
Calling Wait()
0:21.240 SimpleOPAL sippdu.cxx(2052)
Transaction
Sending PDU via connection
0:21.241 SimpleOPAL sippdu.cxx(2054)
Transaction Sent
PDU via connection
0:21.241 SimpleOPAL sippdu.cxx(2073)
Transaction Start
done, Wait()ing for finished
0:37.242 Housekeeper sippdu.cxx(2303) SIP
Signal
transaction as finished
0:37.242 SimpleOPAL sippdu.cxx(2075)
Transaction
finished is ...
0:37.243 SimpleOPAL sipcon.cxx(2698) SIP
Returning from
Wait()
0:37.243 SimpleOPAL sippdu.cxx(2022) SIP
Transaction 1
INFO destroyed.
0:37.244 SimpleOPAL sipcon.cxx(2709) SIP
Calling
OpalConnection::SendUserInputTone
0:37.244 SimpleOPAL connection.cxx(1036)
Connection
Calling rfc2833 handler
0:37.245 SimpleOPAL connection.cxx(1038)
Connection
Returning rfc2833 handler
Sent
The problem seems to be in sippdu.cxx, when running :
finished.Wait()
as the PSyncPoint seems to be released by
"Housekeeper".
But, at the same time, running a tcpdump show that the INFO
message is
followed instantly by a 200 OK :
13:01:15.908425 ref-dev.def.com.com..34060 >
ref-dev.def.com.com..34055: udp
582 (DF)
0x0000 4500 0262 0000 4000 4011 b712 c0a8 0014
E..b.. . .......
0x0010 c0a8 0014 850c 8507 024e 2db5 494e 464f
.........N-.INFO
0x0020 2073 6970 3a73 7570 2e61 6463 6f6d 3140
.sip:sup.adcom1
0x0030 3139 322e 3136 382e 302e 3230 3a33 3430
192.168.0.20:340
0x0040 3535 3b74 7261 6e73 706f 7274 3d75 6470
55;transport=udp
0x0050 2053 4950 2f32 2e30 0d0a 4353 6571 3a20
.SIP/2.0..CSeq:.
0x0060 3120 494e 464f 0d0a 5669 613a 2053 4950
1.INFO..Via:.SIP
0x0070 2f32 2e30 2f55 4450 2031 3932 2e31 3638
/2.0/UDP.192.168
.....
0x01f0 4745 2c49 4e46 4f2c 5049 4e47 0d0a 436f
GE,INFO,PING..Co
0x0200 6e74 656e 742d 5479 7065 3a20 6170 706c
ntent-Type:.appl
0x0210 6963 6174 696f 6e2f 6474 6d66 2d72 656c
ication/dtmf-rel
0x0220 6179 0d0a 436f 6e74 656e 742d 4c65 6e67
ay..Content-Leng
0x0230 7468 3a20 3232 0d0a 4d61 782d 466f 7277
th:.22..Max-Forw
0x0240 6172 6473 3a20 3230 0d0a 0d0a 5369 676e
ards:.20....Sign
0x0250 616c 3d32 0d0a 4475 7261 7469 6f6e 3d30
al=2..Duration=0
0x0260 0d0a ..
13:01:15.916301 ref-dev.def.com.com..34055 >
ref-dev.def.com.com..34060: udp
403 (DF)
0x0000 4500 01af 0000 4000 4011 b7c5 c0a8 0014
E..... . .......
0x0010 c0a8 0014 8507 850c 019b 9748 5349 502f
...........HSIP/
0x0020 322e 3020 3230 3020 4f4b 0d0a 4353 6571
2.0.200.OK..CSeq
0x0030 3a20 3120 494e 464f 0d0a 5669 613a 2053
:.1.INFO..Via:.S
0x0040 4950 2f32 2e30 2f55 4450 2031 3932 2e31
IP/2.0/UDP.192.1
0x0050 3638 2e30 2e32 303a 3334 3036 300d 0a46
68.0.20:34060..F
0x0060 726f 6d3a 203c 7369 703a 7573 6572 4031
rom:.<sip:user 1
...
0x0170 5945 2c43 414e 4345 4c2c 4e4f 5449 4659
YE,CANCEL,NOTIFY
0x0180 2c52 4546 4552 2c4d 4553 5341 4745 2c49
,REFER,MESSAGE,I
0x0190 4e46 4f2c 5049 4e47 0d0a 436f 6e74 656e
NFO,PING..Conten
0x01a0 742d 4c65 6e67 7468 3a20 300d 0a0d 0a
t-Length:.0....
It does look as if the "200 OK" message is not
handled...
Any idea ?
Regards,
Paul
------------------------------------------------------------
------------
Check the FAQ before asking! - http://www.
openh323.org/~openh323/fom.cgi
The OpenH323 Project mailing list, using Mailman. To
unsubscribe or
change your subscription options, goto
htt
p://www.openh323.org/mailman/listinfo/openh323
Maintained by Quicknet Technologies, Inc - http://www.quicknet.net
------------------------------------------------------------
------------
|