Hi, I read in http://kamailio.org/docs/modules/1.4.x/nathelper.html that Kamailio might rewrite ip address in o= in SDP to facilitate NAT traversal.
It may decide to use to original IP or use IP of RTP server. What factors affect its decision ?
1 mar 2013 kl. 04:39 skrev Khoa Pham onmyway133@gmail.com:
Hi, I read in http://kamailio.org/docs/modules/1.4.x/nathelper.html that Kamailio might rewrite ip address in o= in SDP to facilitate NAT traversal.
It may decide to use to original IP or use IP of RTP server. What factors affect its decision ?
Please do not retransmit the same mail to multiple mailing lists. The sr-dev is for development of the source code of Kamailio and this question is related to usage of Kamailio.
Thank you for your understanding.
/O
Le 2013-03-01 07:57, Olle E. Johansson a écrit :
Please do not retransmit the same mail to multiple mailing lists.
Cross-posting could be detected and prevented with some procmail magic. Just reply with a generic "You shall not cross-post" message to incoming mail that have both sr-dev and sr-users in the To: header. Problem solved, with free luser education as a bonus. :)
Simon
Hello,
I think that there are some circumstances where cross posting is desirable. For example, when Daniel is putting out announcements about releases and upcoming events. Cross-posting was also used when the community was arranging a get-together at FOSDEM. Kamailio developers and users all turned up to this meeting and some were people who primarily read sr-dev and others primarily read sr-users.
A blanket stop on cross-posting is probably a bad idea - but cross-posting should be a relatively rare event. I think any education should be about using the right list for the right things. Using Kamailio questions to sr-users and developer discussion to sr-dev.
Regards,
Peter
On 01/03/13 10:20, Simon Perreault wrote:
Le 2013-03-01 07:57, Olle E. Johansson a écrit :
Please do not retransmit the same mail to multiple mailing lists.
Cross-posting could be detected and prevented with some procmail magic. Just reply with a generic "You shall not cross-post" message to incoming mail that have both sr-dev and sr-users in the To: header. Problem solved, with free luser education as a bonus. :)
Simon
1 mar 2013 kl. 11:30 skrev Peter Dunkley peter.dunkley@crocodile-rcs.com:
Hello,
I think that there are some circumstances where cross posting is desirable. For example, when Daniel is putting out announcements about releases and upcoming events. Cross-posting was also used when the community was arranging a get-together at FOSDEM. Kamailio developers and users all turned up to this meeting and some were people who primarily read sr-dev and others primarily read sr-users.
A blanket stop on cross-posting is probably a bad idea - but cross-posting should be a relatively rare event. I think any education should be about using the right list for the right things. Using Kamailio questions to sr-users and developer discussion to sr-dev.
Absolutely. Also, make sure people understand that sr-dev is not second level support, somewhere you go when you don't get an answer on sr-users...
I've tried to clarify and repeat the rules on the mailing list page: http://www.kamailio.org/w/mailing-lists/
Any comments, feedback? /O
1 mar 2013 kl. 11:20 skrev Simon Perreault simon.perreault@viagenie.ca:
Le 2013-03-01 07:57, Olle E. Johansson a écrit :
Please do not retransmit the same mail to multiple mailing lists.
Cross-posting could be detected and prevented with some procmail magic. Just reply with a generic "You shall not cross-post" message to incoming mail that have both sr-dev and sr-users in the To: header. Problem solved, with free luser education as a bonus. :)
Well, that works if they send the same email at the same time to both addresses. That wasn't the case here. Just the same content.
/O :-)
Le 2013-03-01 11:50, Olle E. Johansson a écrit :
Please do not retransmit the same mail to multiple mailing lists.
Cross-posting could be detected and prevented with some procmail magic. Just reply with a generic "You shall not cross-post" message to incoming mail that have both sr-dev and sr-users in the To: header. Problem solved, with free luser education as a bonus. :)
Well, that works if they send the same email at the same time to both addresses. That wasn't the case here. Just the same content.
The "same email to both lists" type are the worst, because then all the replies end up in both lists. I can live with allowing the same content to multiple lists. ;)
(Same content to multiple lists could be used for announcements and such "legitimate" cross-posts.)
Anyway, I'm not complaining, just trying to share ideas of solutions...
Simon
-
Khoa Pham -
Olle E. Johansson -
Peter Dunkley -
Simon Perreault