[Spce-user] Cable modem reinvite NAT issue.
Kelemen Árpád
arpad.kelemen at g-online.hu
Thu Nov 10 10:27:30 EST 2011
Hi all,
changing the session_expires variable from
/etc/ngcp-config/templates/etc/sems/etc/ngcp.sbcprofile.conf.tt2 solved
my issue temporary.
Árpád
On 11/8/2011 4:23 PM, Kelemen Árpád wrote:
>
> Hi All,
>
> In the rtp.log I find the following:
>
>
> Nov 8 16:03:23 sip mediaproxy-ng: Got valid command from
> udp:127.0.0.1:52252: 2150_8 US f4ba5995ce2e6352 78.131.7.9 16454
> 2AB9DEFD-4EB94424000EFC17-7935A700;1 8c23134673;1
> Nov 8 16:03:23 sip mediaproxy-ng: [f4ba5995ce2e6352] Opened ports
> 30012/30013 for RTP
> Nov 8 16:03:23 sip mediaproxy-ng: [f4ba5995ce2e6352] Opened ports
> 30014/30015 for RTP
> Nov 8 16:03:23 sip mediaproxy-ng: Got valid command from
> udp:127.0.0.1:52252: 2150_9 US f4ba5995ce2e6352 78.131.7.9 0
> 2AB9DEFD-4EB94424000EFC17-7935A700;2 8c23134673;2
> Nov 8 16:03:23 sip mediaproxy-ng: [f4ba5995ce2e6352] Opened ports
> 30016/30017 for RTP
> Nov 8 16:03:23 sip mediaproxy-ng: [f4ba5995ce2e6352] Opened ports
> 30018/30019 for RTP
> Nov 8 16:03:23 sip mediaproxy-ng: Got valid command from
> udp:127.0.0.1:58801: 2160_8 LS f4ba5995ce2e6352 10.31.1.2 53456
> 2AB9DEFD-4EB94424000EFC17-7935A700;1 8c23134673;1
> Nov 8 16:03:23 sip mediaproxy-ng: Got valid command from
> udp:127.0.0.1:58801: 2160_9 LS f4ba5995ce2e6352 10.31.1.2 53456
> 2AB9DEFD-4EB94424000EFC17-7935A700;2 8c23134673;2
> Nov 8 16:03:23 sip mediaproxy-ng: [f4ba5995ce2e6352] Confirmed peer
> information - 10.31.1.2:53456
> Nov 8 16:03:25 sip mediaproxy-ng: [f4ba5995ce2e6352] Confirmed peer
> information - 78.131.7.9:16454
> Nov 8 16:05:53 sip mediaproxy-ng: Got valid command from
> udp:127.0.0.1:60565: 2168_8 US f4ba5995ce2e6352 78.131.7.9 16454
> 2AB9DEFD-4EB94424000EFC17-7935A700;1 8c23134673;1
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] Opened ports
> 30020/30021 for RTP
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] Opened ports
> 30022/30023 for RTP
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] Re-using
> existing open RTP ports
> Nov 8 16:05:53 sip mediaproxy-ng: Got valid command from
> udp:127.0.0.1:60565: 2168_9 US f4ba5995ce2e6352 78.131.7.9 0
> 2AB9DEFD-4EB94424000EFC17-7935A700;2 8c23134673;2
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] Opened ports
> 30024/30025 for RTP
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] Opened ports
> 30026/30027 for RTP
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 78.131.7.9:16454
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] Confirmed peer
> information - 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: Got valid command from
> udp:127.0.0.1:52252: 2150_10 LS f4ba5995ce2e6352 10.31.1.2 53456
> 2AB9DEFD-4EB94424000EFC17-7935A700;1 8c23134673;1
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] Re-using
> existing open RTP ports
> Nov 8 16:05:53 sip mediaproxy-ng: Got valid command from
> udp:127.0.0.1:52252: 2150_11 LS f4ba5995ce2e6352 10.31.1.2 53456
> 2AB9DEFD-4EB94424000EFC17-7935A700;2 8c23134673;2
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] Re-using
> existing open RTP ports
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] Confirmed peer
> information - 78.131.7.9:16454
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53457
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
> Nov 8 16:05:53 sip mediaproxy-ng: [f4ba5995ce2e6352] RTP packet
> discarded from 10.31.1.2:53456
>
>
>
>
> On 11/7/2011 5:00 PM, Stefan Sayer wrote:
>>
>> o � on 11/07/2011 04:36 PM:
>>> Dear Jonathan,
>>>
>>> I already cross the mentioned posting but unfortunately my issue is
>>> just
>>> one way. In case if the call is between subscribers or the call come
>>> from
>>> PSTN all work perfectly.
>>>
>>> The following log is get from the modem (debug mode). You will see the
>>> INVITE at 13:23:08.610 11/04/2011 "Failed to update call trace info"
>>> and
>>> the BEY at 13:23:19.200 11/04/2011
>>
>> from the log doesn't look like it's got anything to do with session
>> timers or reinvite if the cable modem is sending BYE after just over
>> 10 seconds. Do you at all get RTP to the cable modem in such a call?
>>
>> Stefan
>
--
----------------------------------------------------
Kelemen Árpád
G-Online Kft
1193 Budapest
Víztorony u. 20
----------------------------------------------------
Privileged/Confidential Information may be contained in
this message. If you are not the addressee indicated in
this message (or responsible for delivery of the message
to such person), you may not copy or deliver this message
to anyone. In such a case, you should destroy this
message and kindly notify the sender by reply e-mail.
More information about the Spce-user
mailing list