I'm not calling RTPProxy with any flags.

Hmm what do those extra arguments mean?


On 7/15/10, Klaus Darilion <klaus.mailingli...@pernau.at> wrote:
> I only see 2 differences:
>
> 1. in the nonworking case the callee's request triggers a lookup with
> more arguments "Lc0,100,101" as in the working case "Lc0".
>
> 2. In the non-working case the callee does not change media ports, only
> the caller does.
>
> how do you call force_rtpproxy? (flags?)
>
> maybe one clients das have a broken SDP?
>
> regards
> klaus
>
> Am 15.07.2010 12:53, schrieb Julian Yap:
>> #
>> U 127.0.0.1:51862 ->  127.0.0.1:9000
>>    13408_13 uc0a43718f3-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 lc0a43718f3-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 ua43718f3-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 la43718f3-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,96a43718f3-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 la43718f3-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 da43718f3-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 uc0ff761399-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 uff761399-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 lff761399-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 dff761399-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
>>
>

-- 
Sent from my mobile device

_______________________________________________
Users mailing list
Users@rtpproxy.org
http://lists.rtpproxy.org/mailman/listinfo/users

Reply via email to