On 07/09/13 07:44, Juha Heinanen wrote:
> i got so far that my sip proxy started ok and was able to connect to
> mediaproxy-ng. i see in syslog these kind of messages:
>
> Jul 9 14:40:11 siika /usr/sbin/sip-proxy[10499]: INFO: rtpproxy-ng
> [rtpproxy.c:1410]: rtpp_test(): rtp proxy <udp:127.0.0.1:25060> found,
> support for it enabled
> Jul 9 14:40:11 siika mediaproxy-ng[8678]: Got valid command from
> 127.0.0.1:39880: ping - { "command": "ping" }
> Jul 9 14:40:11 siika mediaproxy-ng[8678]: Returning to SIP proxy:
> d6:result4:ponge
>
> those kind of syslog message are useful in testing phase, but a
> mediaroxy-ng debug level option (info, warn, error) would be useful for
> production. is that in the works?No, but it would be fairly trivial to implement. On the other hand, syslog messages can be filtered on the syslogd side of things, so I'm not sure this is really necessary. cheers
signature.asc
Description: OpenPGP digital signature
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
