Hi Brian,
I would suggest a complete ngrep dump here for the calls you want to
troubleshoot. It could be that something is wrong into your openser
routing script.
DanB
On Dec 6, 2007 7:44 PM, Brian Heath <brian(a)telethra.com> wrote:
So I'm trying to diagnose an intermittent bug we seem to be having, and I'm
not sure if Mediaproxy's the cause or not...
When a call is made through our system, and then the call is ended normally,
the logs show the following mediaproxy entries:
Dec 6 12:14:02 server01 mediaproxy[14777]: delete
7dfafbf931195f8b61d7bbea68f9c0f8(a)xxx.xxx.xxx.xx1 info=
Dec 6 12:14:02 server01 mediaproxy[14777]: execution time: 0.20 ms
It seems to be pretty standard stuff, really. However, if a call is not
made from behind a firewall, why is mediaproxy even running? Alas, this is
not my main problem...
Every once in a while, calls get dropped. It happens more frequently than
is acceptable. One common thing I've noticed when this happens, is
mediaproxy will log a 'request' and start a session, and then approximately
30 seconds later, the call will be terminated.
Take this one for example. A customer originated a call this morning at Dec
6 11:25:18. Half an hour later, mediaproxy terminated the call. This was
the log entry:
Dec 6 11:55:37 server01 mediaproxy[14777]: request
551afd3c247e7ddc5e8506d753494a3f(a)xxx.xxx.xxx.xx1 xxx.xxx.xxx.xx2:10508:audio
xxx.xxx.xxx.xx2
sip.mydomain.com remote xxx.xxx.xxx.xx1 remote Quintum/1.0.0
info=from:1925XXXXXXX@sip.mydomain.com,to:1925XXXXXXX@xxx.xxx.xxx.xx1,fromtag:45364b32-2439a9,totag:as694a235d
Dec 6 11:55:37 server01 mediaproxy[14777]: session
551afd3c247e7ddc5e8506d753494a3f(a)xxx.xxx.xxx.xx1: started. listening on
xxx.xxx.xxx.xx3:60490
Dec 6 11:55:37 server01 mediaproxy[14777]: execution time: 1.12 ms
Dec 6 11:56:08 server01 mediaproxy[14777]: delete
551afd3c247e7ddc5e8506d753494a3f(a)xxx.xxx.xxx.xx1 info=
Dec 6 11:56:08 server01 mediaproxy[14777]: session
551afd3c247e7ddc5e8506d753494a3f(a)xxx.xxx.xxx.xx1: 0/0/0 packets, 0/0/0 bytes
(caller/called/relayed)
Dec 6 11:56:08 server01 mediaproxy[14777]: session
551afd3c247e7ddc5e8506d753494a3f(a)xxx.xxx.xxx.xx1: ended.
Dec 6 11:56:08 server01 mediaproxy[14777]: execution time: 0.68 ms
Is there any reason why mediaproxy might be arbitrarily loading and starting
a new session, when the call has already long been established? I can't
seem to make heads or tails of this. I'd appreciate any comments or
suggestions.
Thanks,
Brian
This question is also posted at:
http://www.voipuser.org/forum_topic_11777.html
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users