Sure. Thanks for your help! Here's an example of my good trace: # U 127.0.0.1:51862 -> 127.0.0.1:9000 13408_13 Uc0 a43718f3-7e0b-4c1a-90ae-3ebd65fac...@192.168.0.15 8.8.8.15 49200 IPF_PORT_0001_109C;1 # U 127.0.0.1:9000 -> 127.0.0.1:51862 13408_13 12168 9.9.9.50. # U 127.0.0.1:58871 -> 127.0.0.1:9000 13405_9 Lc0 a43718f3-7e0b-4c1a-90ae-3ebd65fac...@192.168.0.15 9.9.9.61 14160 IPF_PORT_0001_109C;1 1c561523917;1 # U 127.0.0.1:9000 -> 127.0.0.1:58871 13405_9 12566 9.9.9.50. # U 127.0.0.1:52919 -> 127.0.0.1:9000 13407_18 U a43718f3-7e0b-4c1a-90ae-3ebd65fac...@192.168.0.15 9.9.9.61 14162 1c561523917;1 IPF_PORT_0001_109C;1 # U 127.0.0.1:9000 -> 127.0.0.1:52919 13407_18 12566 9.9.9.50. # U 127.0.0.1:43011 -> 127.0.0.1:9000 13409_20 L a43718f3-7e0b-4c1a-90ae-3ebd65fac...@192.168.0.15 8.8.8.15 49152 1c561523917;1 IPF_PORT_0001_109C;1 # U 127.0.0.1:9000 -> 127.0.0.1:43011 13409_20 12168 9.9.9.50. # U 127.0.0.1:54320 -> 127.0.0.1:9000 13410_14 Uc0,96 a43718f3-7e0b-4c1a-90ae-3ebd65fac...@192.168.0.15 9.9.9.61 14160 1c561523917;1 IPF_PORT_0001_109C;1 # U 127.0.0.1:9000 -> 127.0.0.1:54320 13410_14 12566 9.9.9.50. # U 127.0.0.1:46744 -> 127.0.0.1:9000 13412_12 L a43718f3-7e0b-4c1a-90ae-3ebd65fac...@192.168.0.15 8.8.8.15 49152 1c561523917;1 IPF_PORT_0001_109C;1 # U 127.0.0.1:9000 -> 127.0.0.1:46744 13412_12 12168 9.9.9.50. # U 127.0.0.1:52919 -> 127.0.0.1:9000 13407_19 D a43718f3-7e0b-4c1a-90ae-3ebd65fac...@192.168.0.15 1c561523917 IPF_PORT_0001_109C # U 127.0.0.1:9000 -> 127.0.0.1:52919 13407_19 0. exit
Here's an example of my non-working trace: # U 127.0.0.1:36929 -> 127.0.0.1:9000 13411_14 Uc0 ff761399-4ace-4691-8667-b56beddaf...@192.168.0.15 8.8.8.15 49200 IPF_PORT_0001_109E;1 # U 127.0.0.1:9000 -> 127.0.0.1:36929 13411_14 15278 9.9.9.50. # U 127.0.0.1:58871 -> 127.0.0.1:9000 13405_10 Lc0,100,101 ff761399-4ace-4691-8667-b56beddaf...@192.168.0.15 8.8.8.123 16458 IPF_PORT_0001_109E;1 27c15b785e7f1003i0;1 # U 127.0.0.1:9000 -> 127.0.0.1:58871 13405_10 17692 9.9.9.50. # U 127.0.0.1:43011 -> 127.0.0.1:9000 13409_21 U ff761399-4ace-4691-8667-b56beddaf...@192.168.0.15 8.8.8.123 16458 27c15b785e7f1003i0;1 IPF_PORT_0001_109E;1 # U 127.0.0.1:9000 -> 127.0.0.1:43011 13409_21 17692 9.9.9.50. # U 127.0.0.1:58871 -> 127.0.0.1:9000 13405_11 L ff761399-4ace-4691-8667-b56beddaf...@192.168.0.15 8.8.8.15 49152 27c15b785e7f1003i0;1 IPF_PORT_0001_109E;1 # U 127.0.0.1:9000 -> 127.0.0.1:58871 13405_11 15278 9.9.9.50. # U 127.0.0.1:43011 -> 127.0.0.1:9000 13409_22 D ff761399-4ace-4691-8667-b56beddaf...@192.168.0.15 IPF_PORT_0001_109E 27c15b785e7f1003i0 # U 127.0.0.1:9000 -> 127.0.0.1:43011 13409_22 0. exit On Wed, Jul 14, 2010 at 9:49 PM, Klaus Darilion <klaus.mailingli...@pernau.at> wrote: > Can you capture the communication between the SIP proxy and rtpproxy? Just > configure rtpproxy and nathelper to use a UDP socket and then use "ngrep -d > lo" > > regards > klaus > > Am 15.07.2010 04:31, schrieb Julian Yap: >> >> Jul 14 16:22:42 INFO:handle_command: new session >> 6e0023a4-f1b3-409f-bd51-2c45ab72f...@192.168.0.15, tag >> IPF_PORT_0001_1091;1 requested, type strong >> Jul 14 16:22:42 INFO:handle_command: new session on a port 19288 >> created, tag IPF_PORT_0001_1091;1 >> Jul 14 16:22:42 INFO:handle_command: pre-filling caller's address with >> 8.8.8.15:49200 >> Jul 14 16:22:42 INFO:handle_command: lookup on ports 19288/13186, >> session timer restarted >> Jul 14 16:22:42 INFO:handle_command: pre-filling callee's address with >> 9.9.9.61:14140 >> Jul 14 16:22:47 INFO:handle_command: adding strong flag to existing >> session, new=1/0/0 >> Jul 14 16:22:47 INFO:handle_command: lookup on ports 19288/13186, >> session timer restarted >> Jul 14 16:22:47 INFO:handle_command: pre-filling callee's address with >> 9.9.9.61:14142 >> Jul 14 16:22:47 INFO:handle_command: lookup on ports 19288/13186, >> session timer restarted >> Jul 14 16:22:47 INFO:handle_command: pre-filling caller's address with >> 8.8.8.15:49152 >> >> ---- >> Jul 14 16:23:58 INFO:handle_command: new session >> c302e635-be7b-4e96-be0c-f69eb9eb5...@192.168.0.15, tag >> IPF_PORT_0001_1093;1 requested, type strong >> Jul 14 16:23:58 INFO:handle_command: new session on a port 11556 >> created, tag IPF_PORT_0001_1093;1 >> Jul 14 16:23:58 INFO:handle_command: pre-filling caller's address with >> 8.8.8.15:49200 >> Jul 14 16:24:05 INFO:handle_command: lookup on ports 11556/13594, >> session timer restarted >> Jul 14 16:24:05 INFO:handle_command: pre-filling callee's address with >> 8.8.8.123:16456 >> Jul 14 16:24:07 INFO:handle_command: adding strong flag to existing >> session, new=1/0/0 >> Jul 14 16:24:07 INFO:handle_command: lookup on ports 11556/13594, >> session timer restarted >> Jul 14 16:24:07 INFO:handle_command: lookup on ports 11556/13594, >> session timer restarted >> Jul 14 16:24:07 INFO:handle_command: pre-filling caller's address with >> 8.8.8.15:49152 >> Jul 14 16:24:07 INFO:rxmit_packets: caller's address filled in: >> 8.8.8.15:49200 (RTP) > _______________________________________________ Users mailing list Users@rtpproxy.org http://lists.rtpproxy.org/mailman/listinfo/users
