On 26/09/14 12:16 PM, Peter Villeneuve wrote:
Hi again.
I've had some users complain that they cannot hangup calls and have to
wait for the default SIP timeout before the client hangs up.
Looking at the kamailio logs, I noticed something strange regarding
RTPengine. What's the deal with the [::]:0 address?
Could this be the cause of the issues users have reported?
I also see in siremis accounting that users indeed try to repeatedly
send out the BYE message to hang up the call but siremis shows a bunch
of 481 responses from kamailio.
I have commented out ipv6 in the /etc/default/rtp/ngcp-rtpengine-daemon
file yet I still see this in the logs:
Sep 26 00:55:19 rtpengine[2950]: [gj0LMNqHnWDBc15BiNAWD7UH29LZfjZD] ---
Tag '', created 1:00 ago, in dialogue with '(none)'
Sep 26 00:55:19 rtpengine[2950]: [gj0LMNqHnWDBc15BiNAWD7UH29LZfjZD]
------ Media #1, port 30034 <> [::]:0 , 0 p, 0 b, 0 e
Sep 26 00:55:19 rtpengine[2950]: [gj0LMNqHnWDBc15BiNAWD7UH29LZfjZD]
------ Media #1, port 30035 <> [::]:0 (RTCP), 0 p, 0 b, 0 e
Sep 26 00:55:19 rtpengine[2950]: [gj0LMNqHnWDBc15BiNAWD7UH29LZfjZD] ---
Tag 'D77HuXhJbqiBg.pBF3LkwC8411VT2Vye', created 1:00 ago, in dialogue
with ''
Sep 26 00:55:19 rtpengine[2950]: [gj0LMNqHnWDBc15BiNAWD7UH29LZfjZD]
------ Media #1, port 30044 <> 190.56.xx.xx:63572, 0 p, 0 b, 0 e
Sep 26 00:55:19 rtpengine[2950]: [gj0LMNqHnWDBc15BiNAWD7UH29LZfjZD]
------ Media #1, port 30045 <> 190.56.xx.xx:3058 (RTCP), 0 p, 0 b, 0 e
I imagine I'm doing something wrong in the config but I'm not sure why I
see an ipv6 address and why the BYEs receive 481 responses.
Any clues as to where I should look?
This indicates that rtpengine never got to see the "answer" part of the
dialogue. The "::" address simply means that no destination address has
been associated yet. All sockets are opened as IPv6 sockets so this is
normal.
cheers
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
