[Serusers] iptelorg

[Miklos Tirpak]

Even if the company was bought by Tekelec, and is focusing on IMS 
developing, iptelorg GmbH is still continuously improving its main 
products, for example SOP (SER Operator Pack) which is targeted to 
service providers. Lots of developers you can see on the mailing list 
are working for Tekelec/iptelorg. So www.iptelorg.com is still nearly 
up-to-date, you can contact us if you need more information.

You can also check IPTEGO's web site (www.iptego.de), the company is 
located in Germany.

Regards,
Miklos

Greger V. Teigre wrote:
> iptelorg.com was bought by Tekelec. I don't think they do 
> support/installation for new customers anymore.
> Others who work a lot on ser/openser:
> Portaone
> AG-Projects
> Voice-Sistem
> 
> g-)
> 
> Sebastian Gabris wrote:
>> Hi everybody,
>>
>> does somebody know if the iptelorg GmbH is still existent.Visited their homepage www.iptelorg.com and it look pretty unmaintained to me.
>>
>> Is there any other company in Germany who offers support & installation services for SER?
>>
>> Best regards,
>>
>> Sebastian
>>
>> P.S. Congrats to iptel.org for their new homepage, will look closer at it tommorow :-)
>>   
>>> -----Ursprüngliche Nachricht-----
>>> Von: Sebastian Gabris <Sebastian.Gabris at web.de>
>>> Gesendet: 11.08.06 16:21:36
>>> An: ratif at burraqtel.com.p, serusers at iptel.org
>>> Betreff: [Serusers] ser SDP rewrite problem, rtpproxy is not working !!!
>>>     
>>
>>   
>>> Hi,
>>>
>>> got also this problem, did you find a solution?
>>>
>>> Sebastian
>>>
>>> hello there,
>>>
>>> I am working on SER with two network interfaces.
>>>
>>> EP1--------------->(172.16.16.160) SER (192.168.5.1) -------------> EP2
>>>
>>> what happens, SER receives invite from EP1, it reinitiates invite for 
>>> EP2. now what it does is that it writes the external IP i.e. 
>>> 172.16.16.160 in the SDP contact info, where as it should be the 
>>> internal one i.e. 192.168.5.1 ...
>>> now I want to overwrite the SDP contact info in that invite. I have got 
>>> two options to do it one option is to use force_rtp_proxy("ei", 
>>> "192.168.5.1") or use sdp_mangle_ip() function of mangler.so . but they 
>>> are not working for me. when I play around with force_rtp_proxy function 
>>> rtpproxy get crashed and sdp_mangle_ip() is not behaving properly ...... 
>>> whats your experience ?
>>>
>>> I have used ser-0.8.14 and now using ser-0.9.0 with cvs rtpproxy. I am 
>>> running rtpproxy like
>>> rtpproxy -s udp:192.168.5.1 -l 172.16.16.160
>>> and I am using this line in ser.cfg
>>> modparam("nathelper", "rtpproxy_sock", "udp:192.168.5.1")
>>>
>>> I am really stucked please help !!!!
>>>
>>> thanking you
>>>
>>> regards,
>>> -- 
>>> Atif
>>> ______________________________________________________________
>>> Verschicken Sie romantische, coole und witzige Bilder per SMS!
>>> Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
>>>
>>> _______________________________________________
>>> Serusers mailing list
>>> Serusers at lists.iptel.org
>>> http://lists.iptel.org/mailman/listinfo/serusers
>>>     
>>
>>
>> ______________________________________________________________
>> Verschicken Sie romantische, coole und witzige Bilder per SMS!
>> Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
>>
>> _______________________________________________
>> Serusers mailing list
>> Serusers at lists.iptel.org
>> http://lists.iptel.org/mailman/listinfo/serusers
>>
>>
>>   
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers