sr-users May 2010

sr-users@lists.kamailio.org

67 participants
106 discussions

NAT Traversal IPTel example
by Andy Savage 05 May '10

05 May '10

Hi there, I've been setting up SER for a testing server on the local network behind a NAT. I'm having problems understanding how to setup the NAT routing in the configuration file. My understanding is that IPTel has already setup advanced NAT routing on the free service (as per the website). Is it possible to get a copy of the configuration file (atleast the part that has the NAT routing stuff). This would help me immensely in getting proper nat traversal setup as it already works great on the IPTel server. Not sure who I would contact in regards to this, but this seemed like a good place to start. Kind regards, Andy Savage -- "The greatest challenge to any thinker is stating the problem in a way that will allow a solution" - Bertrand Russell Andy Savage Cell Phone: +852 936 34341 Skype ID: andy_savage Linked In: http://www.linkedin.com/in/andysavage

2 1

RTPproxy in bridge mode question
by Uriel Rozenbaum 04 May '10

04 May '10

Guys, I'm successfully using a Kamailio + RTPproxy setup in bridge mode with most of my Gateways. My setup includes two different interfaces one with a public IP and teh other with the private IP. Now I'm facing some slight issue. Some providers won't accept my calls (or calls will have some strange behavior) if the Contact header has an IP out of immediate range. I tried to use fix_nated_contact() function but as per my topology, this function will not change the contact header because the IP is already the one on the interface. Example: U 192.168.200.X:5060 -> 192.168.200.Y:5060 INVITE sip:111160911097@192.168.200.Y SIP/2.0. Via: SIP/2.0/UDP 192.168.200.X:5060;branch=z9hG4bK096baacc;rport. From: "Uriel Rozenbaum" <sip:60911100@192.168.200.X>;tag=as32794d5e. To: <sip:111160911097@192.168.200.Y>. Contact: <sip:60911100@*192.168.200.X*>. U 200.A.A.A:5060 -> 200.B.B.B:5060 INVITE sip:898960911097@200.B.B.B SIP/2.0. Record-Route: <sip:200.A.A.A;r2=on;lr=on;ftag=as32794d5e>. Record-Route: <sip:192.168.200.Y;r2=on;lr=on;ftag=as32794d5e>. Via: SIP/2.0/UDP 200.A.A.A;branch=z9hG4bK5222.14fbf4f7.0. Via: SIP/2.0/UDP 192.168.200.X:5060;received=192.168.200.X;branch=z9hG4bK096baacc;rport=5060. From: "Uriel Rozenbaum" <sip:60911100@192.168.200.X>;tag=as32794d5e. To: <sip:111160911097@192.168.200.Y>. Contact: <sip:60911100@*192.168.200.X*>. Is there any way to let know Kamailio the outgoing IP I'll be using and fix the contact accordingly? I can trigger this change after I know the destination IP. Thanks! Uriel

4 7

kamailio and presence_xml parse error
by Francesco 03 May '10

03 May '10

Thx for reply. This is what i get with patch applied (is not pretty readable, but what i can see is "^M" char that could be the cause of the problem...or in rpid field the status "unknown") May 3 15:50:36 ocs /usr/sbin/kamailio[1858]: ERROR:presence_xml:agregate_ xmls: while parsing xml body message [[<?xml version='1.0' encoding='UTF-8'?><presence xmlns='urn:ietf:params:xml:ns:pidf' xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' entity=' sip:amusso@ocs.ita.wtbts.net <sip%3Aamusso(a)ocs.ita.wtbts.net>'><tuple id='t7164a248'><status><basic>open</basic></status></tuple><dm:person id='pf31ded47'><rpid:activities><rpid:unknown/></rpid:activities></dm:person></presence>P Server^M Content-Length: 0^M ^M ]] May 3 15:50:36 ocs /usr/sbin/kamailio[1858]: ERROR:presence_xml:pres_agg_nbody: while aggregating body May 3 15:51:22 ocs /usr/sbin/kamailio[1855]: ERROR:presence_xml:pres_agg_nbody: while aggregating body May 3 15:51:22 ocs /usr/sbin/kamailio[1856]: ERROR:presence_xml:offline_nbody: while parsing xml memory May 3 15:51:22 ocs /usr/sbin/kamailio[1856]: ERROR:presence_xml:pres_agg_nbody: while constructing offline body May 3 15:51:51 ocs /usr/sbin/kamailio[1857]: ERROR:presence_xml:agregate_xmls: while parsing xml body message [[<?xml version='1.0' encoding='UTF-8'?><presence xmlns='urn:ietf:params:xml:ns:pidf' xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' entity=' sip:fcolista@ocs.ita.wtbts.net <sip%3Afcolista(a)ocs.ita.wtbts.net>'><tuple id='tdd57124f'><status><basic>open</basic></status></tuple><dm:person id='pe22c066e'><rpid:activities><rpid:unknown/></rpid:activities></dm:person></presence>resence>]] May 3 15:51:51 ocs /usr/sbin/kamailio[1857]: ERROR:presence_xml:pres_agg_nbody: while aggregating body May 3 15:52:32 ocs /usr/sbin/kamailio[1856]: ERROR:presence_xml:agregate_xmls: while parsing xml body message [[<?xml version='1.0' encoding='UTF-8'?><presence xmlns='urn:ietf:params:xml:ns:pidf' xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' entity=' sip:amusso@ocs.ita.wtbts.net <sip%3Aamusso(a)ocs.ita.wtbts.net>'><tuple id='t7164a248'><status><basic>open</basic></status></tuple><dm:person id='pf31ded47'><rpid:activities><rpid:unknown/></rpid:activities></dm:person></presence>resence>P Server^M Content-Length: 0^M ^M 74fe7e7c241d"^M Server: AlpineLinux SIP Server^M Content-Length: 0^M ^M ]] May 3 15:52:32 ocs /usr/sbin/kamailio[1856]: ERROR:presence_xml:pres_agg_nbody: while aggregating body May 3 15:53:26 ocs /usr/sbin/kamailio[1858]: ERROR:presence_xml:agregate_xmls: while parsing xml body message [[<?xml version='1.0' encoding='UTF-8'?><presence xmlns='urn:ietf:params:xml:ns:pidf' xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' entity=' sip:amusso@ocs.ita.wtbts.net <sip%3Aamusso(a)ocs.ita.wtbts.net>'><tuple id='t7164a248'><status><basic>open</basic></status></tuple><dm:person id='pf31ded47'><rpid:activities><rpid:unknown/></rpid:activities></dm:person></presence>e> tbts.net", nonce="4bded515000000284f85e37237864bdc5da8d6836da5a769"^M Server: AlpineLinux SIP Server^M Content-Length: 0^M ^M ]] May 3 15:53:26 ocs /usr/sbin/kamailio[1858]: ERROR:presence_xml:pres_agg_nbody: while aggregating body :: Francesco Colista :: Email : francesco.colista(a)gmail.com :: Jabber: francesco(a)jabber.org

1 0

[Kamailio-Users] re : openserctl statistics..
by Jignesh Gandhi 03 May '10

03 May '10

Hello, What does the following stat mean when you run the " openserctl moni " sl: received_ACKs = xxxx I did some digging and I got the following explanation... But am not sure if this is an error in operser or an error on a message received by openser or what? " sl: received_ACKs - number of received ACKs due sending negative replies. " any help is appreciated. thanks, --Jignesh

6 11

Add header on failure Route
by Alex Rendour 03 May '10

03 May '10

Hi, We need to add header on the failure route. Exemple: On failure 404 Not found, we need add header Reason: Q.850; cause=1 We tried this in failure_route: if(t_check_status("404")){ xlog("L_ERR", "404 Not found\n"); append_to_reply("Reason: Q.850; cause=1\r\n"); xlog("L_ERR", "404 Not found apres\n"); exit; } and if(t_check_status("404")){ xlog("L_ERR", "404 Not found\n"); append_hf("Reason: Q.850; cause=1\r\n"); xlog("L_ERR", "404 Not found apres\n"); exit; } The twice doesn't work. Someone can help me? Thanks, -- Alexandre Rendour Acropolis Telecom <http://www.acropolistelecom.net> <mailto:rendour@acropolistelecom.net> Adresse : 161-163 avenue Gallieni Paris - Porte de Bagnolet 93170 Bagnolet

2 2

Simple Trunking with Kamailio
by Jared Martin 01 May '10

01 May '10

Ok, this is probably an easy question: Say I have my kamailio server set up and all of my voip clients are gleefully calling each other... but now I want to connect them to the PSTN. Can I set up kamailo to trunk calls using a few grandstream gateways? or is Asterisk neccesary? Sorry if the answers out there, but I haven't found anything that answered the question directly. I'm a linux admin, but I'm new to PBX's and the like. I've installed kamailio in the past using instructions specific to that situation, but haven't configured trunking (or I didn't recognize thats what it was) references to howtos or tutorials would also be greatly appreciated Thanks for your help, Jared Martin

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users May 2010