Hi Helge,

the problem was that the OSP module was directly using the RR function ( and not via RR API), which was leading to some incompatibility in function prototype . For ex, the RR export to the script a function that support pseudo-variables as parameter, but internally, the RR API exports the function with only text support as parameter..

I adjusted the OSP module to use the RR and TM APIs, but I was not able to test even if it compiles properly since I do not have the OSP devel stuff installed.

please update from cvs and let me know if the problem is fixed.

thanks for report and regards, bogdan

Helge Waastad wrote:

Hi, and a good evening to you all. I'm having a beer (or two) and found out that I oughta try something "new" :-)

I've started (I've done it successfully before, but then in a standalone server scenario) to implement the OSP module for peering. However, I see in my logs, that OpenSER is complaining about buffer sizes...... What I'm worried about is the ERROR message beneath. I'm afraid that this is messing up my routing.

Any comments?

osp: there is 1 osp routes, call-id '692039019@10.0.0.18', transaction-id '1142102578275' Mar 11 19:42:58 proxy-02 /usr/sbin/openser[21464]: xl_printf: no more space for text [1950183213] Mar 11 19:42:58 proxy-02 /usr/sbin/openser[21464]: xl_printf: buffer overflow -- increase the buffer size... Mar 11 19:42:58 proxy-02 /usr/sbin/openser[21464]: ERROR:rr:w_add_rr_param: failed to print the format

---

---

Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users