sr-users

sr-users@lists.kamailio.org

20 participants
37472 discussions

Re: [Kamailio-Users] I don't have asterisk audio to openser - mediaproxy
by Ricky Gutierrez 30 Oct '08

30 Oct '08

Hi luzano thank you for your help and time, this it is my full ngrep. I have asterisk, mediaproxy and openser together in the same pc I have the doubt that when a incoming call from the PSTN by asterisk, sends it to an extension of openser, to which I do not request authentication to him within invites, I believe that there it is where I have problems with mediaproxy that it leaves you want to see of the openser.cfg, or everything? regards .. interface: any filter: (ip) and ( port 5060 ) # U +0.063740 192.168.10.1:5070 -> 192.168.10.1:5060 INVITE sip:113@192.168.10.1 SIP/2.0 Via: SIP/2.0/UDP 192.168.10.1:5070;branch=z9hG4bK3716ee27;rport From: "asterisk" <sip:asterisk@192.168.10.1:5070>;tag=as30de9085 To: <sip:113@192.168.10.1> Contact: <sip:asterisk@192.168.10.1:5070> Call-ID: 373456b8787e65d9764158381c9da273(a)192.168.10.1 CSeq: 102 INVITE User-Agent: Asterisk PBX Max-Forwards: 70 Date: Wed, 29 Oct 2008 16:26:18 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Type: application/sdp Content-Length: 238 v=0 o=root 9850 9850 IN IP4 192.168.10.1 s=session c=IN IP4 192.168.10.1 t=0 0 m=audio 14750 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - a=ptime:20 a=sendrecv # U +0.004203 192.168.10.1:5060 -> 192.168.10.1:5070 SIP/2.0 100 Giving a try Via: SIP/2.0/UDP 192.168.10.1:5070;branch=z9hG4bK3716ee27;rport=5070 From: "asterisk" <sip:asterisk@192.168.10.1:5070>;tag=as30de9085 To: <sip:113@192.168.10.1> Call-ID: 373456b8787e65d9764158381c9da273(a)192.168.10.1 CSeq: 102 INVITE Server: OpenSER (1.3.2-notls (i386/linux)) Content-Length: 0 # U +0.000275 192.168.10.1:5060 -> 192.168.10.30:5062 INVITE sip:113@192.168.10.30:5062;transport=udp SIP/2.0 Record-Route: <sip:192.168.10.1;lr=on;ftag=as30de9085;nat=yes> Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK7ce3.dd78e5e3.0 Via: SIP/2.0/UDP 192.168.10.1:5070;branch=z9hG4bK3716ee27;rport=5070 From: "asterisk" <sip:asterisk@192.168.10.1:5070>;tag=as30de9085 To: <sip:113@192.168.10.1> Contact: <sip:asterisk@192.168.10.1:5070> Call-ID: 373456b8787e65d9764158381c9da273(a)192.168.10.1 CSeq: 102 INVITE User-Agent: Asterisk PBX Max-Forwards: 69 Date: Wed, 29 Oct 2008 16:26:18 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Type: application/sdp Content-Length: 238 P-hint: route(3)|setflag7,forcerport,fix_contact P-hint: inbound->inbound P-hint: Route[6]: mediaproxy v=0 o=root 9850 9850 IN IP4 192.168.10.1 s=session c=IN IP4 192.168.1.64 t=0 0 m=audio 35058 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - a=ptime:20 a=sendrecv # U +0.026845 192.168.10.30:5062 -> 192.168.10.1:5060 SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK7ce3.dd78e5e3.0 Via: SIP/2.0/UDP 192.168.10.1:5070;branch=z9hG4bK3716ee27;rport=5070 From: "asterisk" <sip:asterisk@192.168.10.1:5070>;tag=as30de9085 To: <sip:113@192.168.10.1> Call-ID: 373456b8787e65d9764158381c9da273(a)192.168.10.1 CSeq: 102 INVITE User-Agent: Grandstream GXP2020 1.1.6.16 Content-Length: 0 # U +0.009886 192.168.10.30:5062 -> 192.168.10.1:5060 SIP/2.0 180 Ringing Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK7ce3.dd78e5e3.0 Via: SIP/2.0/UDP 192.168.10.1:5070;branch=z9hG4bK3716ee27;rport=5070 Record-Route: <sip:192.168.10.1;lr=on;ftag=as30de9085;nat=yes> From: "asterisk" <sip:asterisk@192.168.10.1:5070>;tag=as30de9085 To: <sip:113@192.168.10.1>;tag=21c220c2e075d838 Call-ID: 373456b8787e65d9764158381c9da273(a)192.168.10.1 CSeq: 102 INVITE User-Agent: Grandstream GXP2020 1.1.6.16 Contact: <sip:113@192.168.10.30:5062;transport=udp> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Length: 0 # U +0.000169 192.168.10.1:5060 -> 192.168.10.1:5070 SIP/2.0 180 Ringing Via: SIP/2.0/UDP 192.168.10.1:5070;branch=z9hG4bK3716ee27;rport=5070 Record-Route: <sip:192.168.10.1;lr=on;ftag=as30de9085;nat=yes> From: "asterisk" <sip:asterisk@192.168.10.1:5070>;tag=as30de9085 To: <sip:113@192.168.10.1>;tag=21c220c2e075d838 Call-ID: 373456b8787e65d9764158381c9da273(a)192.168.10.1 CSeq: 102 INVITE User-Agent: Grandstream GXP2020 1.1.6.16 Contact: <sip:113@192.168.10.30:5062;transport=udp> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Length: 0 P-hint: Onreply-route - fixcontact # U +0.000140 190.184.35.4:5060 -> 192.168.1.64:5064 OPTIONS sip:130@192.168.1.64:5064 SIP/2.0 Via: SIP/2.0/UDP 190.184.35.4:5060;branch=z9hG4bK715ee282;rport From: "asterisk" <sip:asterisk@190.184.35.4>;tag=as35db6300 To: <sip:130@192.168.1.64:5064> Contact: <sip:asterisk@190.184.35.4> Call-ID: 16e287fc2b24afb97eb1759952eff3d3(a)190.184.35.4 CSeq: 102 OPTIONS User-Agent: Asterisk PBX Max-Forwards: 70 Date: Wed, 29 Oct 2008 16:26:18 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Length: 0 # U +0.000017 190.184.35.4:5060 -> 192.168.10.19:5064 OPTIONS sip:130@192.168.1.64:5064 SIP/2.0 Via: SIP/2.0/UDP 190.184.35.4:5060;branch=z9hG4bK715ee282;rport From: "asterisk" <sip:asterisk@190.184.35.4>;tag=as35db6300 To: <sip:130@192.168.1.64:5064> Contact: <sip:asterisk@190.184.35.4> Call-ID: 16e287fc2b24afb97eb1759952eff3d3(a)190.184.35.4 CSeq: 102 OPTIONS User-Agent: Asterisk PBX Max-Forwards: 70 Date: Wed, 29 Oct 2008 16:26:18 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Length: 0 # U +0.008208 192.168.10.19:5064 -> 190.184.35.4:5060 SIP/2.0 200 OK To: <sip:130@192.168.1.64:5064>;tag=9611a90af8ab9321i1 From: "asterisk" <sip:asterisk@190.184.35.4>;tag=as35db6300 Call-ID: 16e287fc2b24afb97eb1759952eff3d3(a)190.184.35.4 CSeq: 102 OPTIONS Via: SIP/2.0/UDP 190.184.35.4:5060;branch=z9hG4bK715ee282 Server: Linksys/SPA942-5.2.8 Content-Length: 0 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces # U +0.000014 192.168.1.64:5064 -> 190.184.35.4:5060 SIP/2.0 200 OK To: <sip:130@192.168.1.64:5064>;tag=9611a90af8ab9321i1 From: "asterisk" <sip:asterisk@190.184.35.4>;tag=as35db6300 Call-ID: 16e287fc2b24afb97eb1759952eff3d3(a)190.184.35.4 CSeq: 102 OPTIONS Via: SIP/2.0/UDP 190.184.35.4:5060;branch=z9hG4bK715ee282 Server: Linksys/SPA942-5.2.8 Content-Length: 0 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces # U +0.956449 192.168.10.19:5064 -> 190.184.35.4:5060 NOTIFY sip:190.184.35.4 SIP/2.0 Via: SIP/2.0/UDP 192.168.10.19:5064;branch=z9hG4bK-5ade1219 From: <sip:130@190.184.35.4>;tag=7c3557f6145bd125o1 To: <sip:190.184.35.4> Call-ID: ce8ea9b2-baee4a99(a)192.168.10.19 CSeq: 12 NOTIFY Max-Forwards: 70 Event: keep-alive User-Agent: Linksys/SPA942-5.2.8 Content-Length: 0 # U +0.000027 192.168.1.64:5064 -> 190.184.35.4:5060 NOTIFY sip:190.184.35.4 SIP/2.0 Via: SIP/2.0/UDP 192.168.10.19:5064;branch=z9hG4bK-5ade1219 From: <sip:130@190.184.35.4>;tag=7c3557f6145bd125o1 To: <sip:190.184.35.4> Call-ID: ce8ea9b2-baee4a99(a)192.168.10.19 CSeq: 12 NOTIFY Max-Forwards: 70 Event: keep-alive User-Agent: Linksys/SPA942-5.2.8 Content-Length: 0 # U +0.156145 190.184.35.4:5060 -> 192.168.1.64:5064 SIP/2.0 489 Bad event Via: SIP/2.0/UDP 192.168.10.19:5064;branch=z9hG4bK-5ade1219;received=192.168.1.64 From: <sip:130@190.184.35.4>;tag=7c3557f6145bd125o1 To: <sip:190.184.35.4>;tag=as2002c003 Call-ID: ce8ea9b2-baee4a99(a)192.168.10.19 CSeq: 12 NOTIFY User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Length: 0 # U +0.000017 190.184.35.4:5060 -> 192.168.10.19:5064 SIP/2.0 489 Bad event Via: SIP/2.0/UDP 192.168.10.19:5064;branch=z9hG4bK-5ade1219;received=192.168.1.64 From: <sip:130@190.184.35.4>;tag=7c3557f6145bd125o1 To: <sip:190.184.35.4>;tag=as2002c003 Call-ID: ce8ea9b2-baee4a99(a)192.168.10.19 CSeq: 12 NOTIFY User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Length: 0 # U +5.895003 192.168.10.30:5062 -> 192.168.10.1:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK7ce3.dd78e5e3.0 Via: SIP/2.0/UDP 192.168.10.1:5070;branch=z9hG4bK3716ee27;rport=5070 Record-Route: <sip:192.168.10.1;lr=on;ftag=as30de9085;nat=yes> From: "asterisk" <sip:asterisk@192.168.10.1:5070>;tag=as30de9085 To: <sip:113@192.168.10.1>;tag=21c220c2e075d838 Call-ID: 373456b8787e65d9764158381c9da273(a)192.168.10.1 CSeq: 102 INVITE User-Agent: Grandstream GXP2020 1.1.6.16 Contact: <sip:113@192.168.10.30:5062;transport=udp> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Type: application/sdp Supported: replaces, timer Content-Length: 212 v=0 o=113 8000 8000 IN IP4 192.168.10.30 s=SIP Call c=IN IP4 192.168.10.30 t=0 0 m=audio 5004 RTP/AVP 0 101 a=sendrecv a=rtpmap:0 PCMU/8000 a=ptime:20 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11 # U +0.001400 192.168.10.1:5060 -> 192.168.10.1:5070 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.10.1:5070;branch=z9hG4bK3716ee27;rport=5070 Record-Route: <sip:192.168.10.1;lr=on;ftag=as30de9085;nat=yes> From: "asterisk" <sip:asterisk@192.168.10.1:5070>;tag=as30de9085 To: <sip:113@192.168.10.1>;tag=21c220c2e075d838 Call-ID: 373456b8787e65d9764158381c9da273(a)192.168.10.1 CSeq: 102 INVITE User-Agent: Grandstream GXP2020 1.1.6.16 Contact: <sip:113@192.168.10.30:5062;transport=udp> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Type: application/sdp Supported: replaces, timer Content-Length: 212 P-hint: Onreply-route - fixcontact P-hint: onreply_route|usemediaproxy v=0 o=113 8000 8000 IN IP4 192.168.10.30 s=SIP Call c=IN IP4 192.168.1.64 t=0 0 m=audio 35058 RTP/AVP 0 101 a=sendrecv a=rtpmap:0 PCMU/8000 a=ptime:20 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11 # U +0.000557 192.168.10.1:5070 -> 192.168.10.1:5060 ACK sip:113@192.168.10.30:5062;transport=udp SIP/2.0 Via: SIP/2.0/UDP 192.168.10.1:5070;branch=z9hG4bK3f155ae6;rport Route: <sip:192.168.10.1;lr=on;ftag=as30de9085;nat=yes> From: "asterisk" <sip:asterisk@192.168.10.1:5070>;tag=as30de9085 To: <sip:113@192.168.10.1>;tag=21c220c2e075d838 Contact: <sip:asterisk@192.168.10.1:5070> Call-ID: 373456b8787e65d9764158381c9da273(a)192.168.10.1 CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 70 Content-Length: 0 # U +0.000215 192.168.10.1:5060 -> 192.168.10.30:5062 ACK sip:113@192.168.10.30:5062;transport=udp SIP/2.0 Record-Route: <sip:192.168.10.1;lr=on;ftag=as30de9085;nat=yes> Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK7ce3.dd78e5e3.2 Via: SIP/2.0/UDP 192.168.10.1:5070;branch=z9hG4bK3f155ae6;rport=5070 From: "asterisk" <sip:asterisk@192.168.10.1:5070>;tag=as30de9085 To: <sip:113@192.168.10.1>;tag=21c220c2e075d838 Contact: <sip:asterisk@192.168.10.1:5070> Call-ID: 373456b8787e65d9764158381c9da273(a)192.168.10.1 CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 69 Content-Length: 0 P-hint: LR|fixcontact,setflag6 # U +0.886545 192.168.10.28:5060 -> 192.168.10.1:5060 ________________________________ From: luzango mfupe <luzango.mfupe(a)gmail.com> To: users(a)lists.kamailio.org Sent: Wednesday, October 29, 2008 5:12:29 AM Subject: Re: [Kamailio-Users] I don't have asterisk audio to openser - mediaproxy Hi Ricky, Where is your Kamailio config?? is this your full ngrep capture?? Rgds, Luzango.

2 1

[Kamailio-Users] kamailio and rtpproxy-no audio
by Fabian Borot 30 Oct '08

30 Oct '08

hello I am trying to use rtpproxy and kamailio. Below please find my kamailio.cfg file. But this is what is happening: 1- ext 101[IP 76.109.183.2] is able to send audio to kamailio's IP [65.111.185.187]but it does not reach ext 100 IP [76.109.15.75]. 2- ext 100 does not send RTP at all. 3- I still see the private IPs in the SDPs of both exts. I am aattaching a wireshark capture Thank you in advance Fabian # $Id: kamailio.cfg 4576 2008-08-05 16:22:38Z klaus_darilion $ # # Kamailion basic configuration script # by Anca Vamanu <anca(a)voice-system.ro> # # Please refer to the Core CookBook at http://www.kamailio.org/dokuwiki/doku.php # for a explanation of possible statements, functions and parameters. # ####### Global Parameters ######### debug=3 log_stderror=no log_facility=LOG_LOCAL0 fork=yes children=4 /* uncomment the following lines to enable debugging */ #debug=6 #fork=no #log_stderror=yes /* uncomment the next line to disable TCP (default on) */ disable_tcp=yes /* uncomment the next line to enable the auto temporary blacklisting of not available destinations (default disabled) */ #disable_dns_blacklist=no /* uncomment the next line to enable IPv6 lookup after IPv4 dns lookup failures (default disabled) */ #dns_try_ipv6=yes /* uncomment the next line to disable the auto discovery of local aliases based on revers DNS on IPs (default on) */ #auto_aliases=no /* uncomment the following lines to enable TLS support (default off) */ #disable_tls = no #listen = tls:your_IP:5061 #tls_verify_server = 1 #tls_verify_client = 1 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = '/usr/local/etc/kamailio/tls/user/user-cert.pem' #tls_private_key = '/usr/local/etc/kamailio/tls/user/user-privkey.pem' #tls_ca_list = '/usr/local/etc/kamailio/tls/user/user-calist.pem' port=5060 /* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ listen=udp:65.111.185.187:5060 ####### Modules Section ######## #set module path mpath='/usr/local/lib/kamailio/modules/' /* uncomment next line for MySQL DB support */ loadmodule 'db_mysql.so' loadmodule 'sl.so' loadmodule 'tm.so' loadmodule 'rr.so' loadmodule 'maxfwd.so' loadmodule 'usrloc.so' loadmodule 'registrar.so' loadmodule 'textops.so' loadmodule 'mi_fifo.so' loadmodule 'uri_db.so' loadmodule 'uri.so' loadmodule 'xlog.so' loadmodule 'acc.so' /* uncomment next lines for MySQL based authentication support NOTE: a DB (like db_mysql) module must be also loaded */ loadmodule 'auth.so' loadmodule 'auth_db.so' /* uncomment next line for aliases support NOTE: a DB (like db_mysql) module must be also loaded */ #loadmodule 'alias_db.so' /* uncomment next line for multi-domain support NOTE: a DB (like db_mysql) module must be also loaded NOTE: be sure and enable multi-domain support in all used modules (see 'multi-module params' section ) */ #loadmodule 'domain.so' /* uncomment the next two lines for presence server support NOTE: a DB (like db_mysql) module must be also loaded */ #loadmodule 'presence.so' #loadmodule 'presence_xml.so' loadmodule 'nathelper.so' # ----------------- setting module-specific parameters --------------- # ----- mi_fifo params ----- modparam('mi_fifo', 'fifo_name', '/tmp/kamailio_fifo') # ----- rr params ----- # add value to ;lr param to cope with most of the UAs modparam('rr', 'enable_full_lr', 1) # do not append from tag to the RR (no need for this script) modparam('rr', 'append_fromtag', 0) # ----- rr params ----- modparam('registrar', 'method_filtering', 1) /* uncomment the next line to disable parallel forking via location */ # modparam('registrar', 'append_branches', 0) /* uncomment the next line not to allow more than 10 contacts per AOR */ #modparam('registrar', 'max_contacts', 10) # ----- uri_db params ----- /* by default we disable the DB support in the module as we do not need it in this configuration */ modparam('uri_db', 'use_uri_table', 0) modparam('uri_db', 'db_url', '') # ----- acc params ----- /* what sepcial events should be accounted ? */ modparam('acc', 'early_media', 1) modparam('acc', 'report_ack', 1) modparam('acc', 'report_cancels', 1) /* by default ww do not adjust the direct of the sequential requests. if you enable this parameter, be sure the enable 'append_fromtag' in 'rr' module */ modparam('acc', 'detect_direction', 0) /* account triggers (flags) */ modparam('acc', 'failed_transaction_flag', 3) modparam('acc', 'log_flag', 1) modparam('acc', 'log_missed_flag', 2) /* uncomment the following lines to enable DB accounting also */ modparam('acc', 'db_flag', 1) modparam('acc', 'db_missed_flag', 2) # ----- usrloc params ----- modparam('usrloc', 'db_mode', 0) /* uncomment the following lines if you want to enable DB persistency for location entries */ modparam('usrloc', 'db_mode', 2) #modparam('usrloc', 'db_url', # 'mysql://openser:openserrw@localhost/openser') modparam('usrloc', 'nat_bflag', 3) # ----- auth_db params ----- /* uncomment the following lines if you want to enable the DB based authentication */ modparam('auth_db', 'calculate_ha1', yes) modparam('auth_db', 'password_column', 'password') modparam('auth_db', 'db_url', 'mysql://openser:openserrw@localhost/openser') modparam('auth_db', 'load_credentials', '') # ----- alias_db params ----- /* uncomment the following lines if you want to enable the DB based aliases */ #modparam('alias_db', 'db_url', # 'mysql://openser:openserrw@localhost/openser') # ----- domain params ----- /* uncomment the following lines to enable multi-domain detection support */ #modparam('domain', 'db_url', # 'mysql://openser:openserrw@localhost/openser') #modparam('domain', 'db_mode', 1) # Use caching # ----- multi-module params ----- /* uncomment the following line if you want to enable multi-domain support in the modules (dafault off) */ #modparam('alias_db|auth_db|usrloc|uri_db', 'use_domain', 1) # ----- presence params ----- /* uncomment the following lines if you want to enable presence */ #modparam('presence|presence_xml', 'db_url', # 'mysql://openser:openserrw@localhost/openser') #modparam('presence_xml', 'force_active', 1) #modparam('presence', 'server_address', 'sip:192.168.1.2:5060') # ----- nathelper params ----- modparam('nathelper', 'natping_interval', 10) modparam('nathelper', 'ping_nated_only', 1) modparam('nathelper', 'rtpproxy_sock', 'udp:localhost:8899') modparam('nathelper', 'rtpproxy_disable_tout', 20) modparam('nathelper', 'rtpproxy_tout', 2) modparam('nathelper', 'rtpproxy_retr', 2) modparam('nathelper', 'sipping_from', 'sip:pinger@mykamailio.com') modparam('nathelper', 'sipping_bflag', 7) ####### Routing Logic ######## # main request routing logic route{ if (!mf_process_maxfwd_header('10')) { sl_send_reply('483','Too Many Hops'); exit; } if (is_method('REGISTER')) { # authenticate the REGISTER requests (uncomment to enable auth) if (!www_authorize('', 'subscriber')) { www_challenge('', '0'); exit; } if (!save('location')) sl_reply_error(); exit; } if (!lookup('location')) { switch ($retcode) { case -1: case -3: t_newtran(); t_reply('404', 'Not Found'); exit; case -2: sl_send_reply('405', 'Method Not Allowed'); exit; } } # when routing via usrloc, log the missed calls also setflag(2); # record routing if (!is_method('REGISTER|MESSAGE')) { record_route(); } # account only INVITEs if (is_method('INVITE')) { setflag(1); # do accounting } # for INVITEs enable some additional helper routes if (is_method('INVITE')) { force_rtp_proxy(); } if (!t_relay()) { sl_reply_error(); }; exit; # CANCEL processing if (is_method('CANCEL|BYE')) { unforce_rtp_proxy(); if (t_check_trans()) t_relay(); exit; } } _________________________________________________________________ Stay organized with simple drag and drop from Windows Live Hotmail. http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_102008

1 1

[Kamailio-Users] version cdrtool mediaproxy 1.9.1
by Ricky Gutierrez 29 Oct '08

29 Oct '08

Hi nuno, excuse me but that version of cdrtool you used for mediaproxy 1.9.1? , I am trying to do the same a server billing with openser and asterisk .. best regardss rickygm

2 1

Re: [Kamailio-Users] REGISTER port with Xlite 2.0
by ingdavidcespedes＠cable.net.co 29 Oct '08

29 Oct '08

Hi I download Twinkle, and install all the prerequisites, except for Qt. I have some problems with it. First I download Qt for Linux/X11: C++ "qt-x11-opensource-src-4.4.3.tar" I really don't know if it is the one I have to download, because In the Twinkle page, it only says you have to install "Qt for open source (3.3.0 or later, but not Qt4)". Then I do all the steps cd /tmp gunzip qt-x11-opensource-src-4.4.3.tar.gz # uncompress the archive tar xvf qt-x11-opensource-src-4.4.3.tar # unpack it cd /tmp/qt-x11-opensource-src-4.4.3 ./configure #It took more than 6 hours make su -c "make install" Then I retry to install Twinkle entering in Twinkle directory an doing ./configure but I receive the following error: checking for qt-mt >= 3.3.0 qt-mt < 4.0... Package qt-mt was not found in the pkg-config search path. Perhaps you should add the directory containing `qt-mt.pc' to the PKG_CONFIG_PATH environment variable No package 'qt-mt' found Package qt-mt was not found in the pkg-config search path. Perhaps you should add the directory containing `qt-mt.pc' to the PKG_CONFIG_PATH environment variable No package 'qt-mt' found configure: error: Library requirements (qt-mt >= 3.3.0 qt-mt < 4.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. So I read the FAQ of Twinke (http://www.xs4all.nl/~mfnboer/twinkle/index.html) an it says that I can skip this error by doing ./configure --disable-qt-check, but now I receive the following error: checking value of $QTDIR... /usr/lib/qt-3.3 checking for qmake... no configure: error: Cannot find qmake in $QTDIR/bin. $QTDIR is incorrect. So I realize that I didn't have libqt-mt so I try to recompile QT with "./configure -thread" but it didn't let me, so I try with "./configure -DQT_THREAD_SUPPORT" and the compilation took also mother tan 6 hours, and I retry to install Twinkle, but without success, I receive the same message. checking value of $QTDIR... /usr/lib/qt-3.3 checking for qmake... no configure: error: Cannot find qmake in $QTDIR/bin. $QTDIR is incorrect. I don't Know what I am doing wrong. Any Help!!!!! please. David Cespedes. ----- Mensaje original ----- De: Iñaki Baz Castillo <ibc(a)aliax.net> Fecha: Martes, Octubre 28, 2008 8:15 am Asunto: Re: [Kamailio-Users] REGISTER port with Xlite 2.0 > 2008/10/28 Daniel-Constantin Mierla <miconda(a)gmail.com>: > > is twinkle able now to display rich presence status? Last time I > tried> was showing only online/offline status. > > For now just online/offline status. > > But it has other great features as: > - Indication of Message Composition for Instant Messaging - RFC 3994 > - PingPong TCP keepalive. > - TCP/UDP > - PRACK > - q-value in registration. > > For me it's the most reliable softphone. > > > -- > Iñaki Baz Castillo > <ibc(a)aliax.net> > _______________________________________________ > Users mailing list > Users(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >

3 2

Re: [Kamailio-Users] REGISTER port with Xlite 2.0
by ingdavidcespedes＠cable.net.co 29 Oct '08

29 Oct '08

Excuse me list, it was an error copy to this list, but maybe some one can help me. ----- Mensaje original ----- De: Alex Balashov <abalashov(a)evaristesys.com> Fecha: Miércoles, Octubre 29, 2008 11:31 am Asunto: Re: [Kamailio-Users] REGISTER port with Xlite 2.0 > This is not the Twinkle list. > > ingdavidcespedes(a)cable.net.co wrote: > > > Hi > > > > I download Twinkle, and install all the prerequisites, except for > Qt. I have some problems with it. First I download Qt for > Linux/X11: C++ "qt-x11-opensource-src-4.4.3.tar" I really don't > know if it is the one I have to download, because In the Twinkle > page, it only says you have to install "Qt for open source (3.3.0 > or later, but not Qt4)". Then I do all the steps > > > > cd /tmp > > gunzip qt-x11-opensource-src-4.4.3.tar.gz # > uncompress the archive > > tar xvf qt-x11-opensource-src-4.4.3.tar # unpack it > > cd /tmp/qt-x11-opensource-src-4.4.3 > > ./configure #It took more than 6 > hours> make > > su -c "make install" > > Then I retry to install Twinkle entering in Twinkle directory an > doing ./configure but I receive the following error: > > > > checking for qt-mt >= 3.3.0 qt-mt < 4.0... Package qt-mt was not > found in the pkg-config search path. Perhaps you should add the > directory containing `qt-mt.pc' to the PKG_CONFIG_PATH environment > variable No package 'qt-mt' found Package qt-mt was not found in > the pkg-config search path. Perhaps you should add the directory > containing `qt-mt.pc' to the PKG_CONFIG_PATH environment variable > No package 'qt-mt' found > > configure: error: Library requirements (qt-mt >= 3.3.0 qt-mt < > 4.0) not met; consider adjusting the PKG_CONFIG_PATH environment > variable if your libraries are in a nonstandard prefix so pkg- > config can find them. > > > > So I read the FAQ of Twinke > (http://www.xs4all.nl/~mfnboer/twinkle/index.html) an it says that > I can skip this error by doing ./configure --disable-qt-check, but > now I receive the following error: > > > > checking value of $QTDIR... /usr/lib/qt-3.3 > > checking for qmake... no > > configure: error: Cannot find qmake in $QTDIR/bin. $QTDIR is > incorrect.> > > So I realize that I didn't have libqt-mt so I try to recompile QT > with "./configure -thread" but it didn't let me, so I try with > "./configure -DQT_THREAD_SUPPORT" and the compilation took also > mother tan 6 hours, and I retry to install Twinkle, but without > success, I receive the same message. > > > > checking value of $QTDIR... /usr/lib/qt-3.3 > > checking for qmake... no > > configure: error: Cannot find qmake in $QTDIR/bin. $QTDIR is > incorrect.> > > I don't Know what I am doing wrong. Any Help!!!!! please. > > > > David Cespedes. > > > > ----- Mensaje original ----- > > De: Iñaki Baz Castillo <ibc(a)aliax.net> > > Fecha: Martes, Octubre 28, 2008 8:15 am > > Asunto: Re: [Kamailio-Users] REGISTER port with Xlite 2.0 > > > >> 2008/10/28 Daniel-Constantin Mierla <miconda(a)gmail.com>: > >>> is twinkle able now to display rich presence status? Last time > I > >> tried> was showing only online/offline status. > >> > >> For now just online/offline status. > >> > >> But it has other great features as: > >> - Indication of Message Composition for Instant Messaging - RFC > 3994>> - PingPong TCP keepalive. > >> - TCP/UDP > >> - PRACK > >> - q-value in registration. > >> > >> For me it's the most reliable softphone. > >> > >> > >> -- > >> Iñaki Baz Castillo > >> <ibc(a)aliax.net> > >> _______________________________________________ > >> Users mailing list > >> Users(a)lists.kamailio.org > >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > >> > > > > > > _______________________________________________ > > Users mailing list > > Users(a)lists.kamailio.org > > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > > > -- > Alex Balashov > Evariste Systems > Web : http://www.evaristesys.com/ > Tel : (+1) (678) 954-0670 > Direct : (+1) (678) 954-0671 > Mobile : (+1) (706) 338-8599 > > _______________________________________________ > Users mailing list > Users(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >

2 1

[Kamailio-Users] Fwd: How to enable local_route feature ?
by Pascal Maugeri 29 Oct '08

29 Oct '08

Hi Following your instructions I have enable the compilation defined in Makefile.defs and recompile everything after a make clean. One capture of the compilation for you to see the define is enable: [...] gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-stringops -falign-loops -ftree-vectorize -mtune=prescott -Wold-style-definition -Wmissing-field-initializers -Wredundant-decls -DMOD_NAME='"uri_db"' -DNAME='"kamailio"' -DVERSION='"1.4.2-notls"' -DARCH='"i386"' -DOS='"linux"' -DCOMPILER='"gcc 4.0.2"' -D__CPU_i386 -D__OS_linux -D__SMP_yes -DCFG_DIR='"/usr/local/etc/kamailio/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DSTATISTICS -DCHANGEABLE_DEBUG_LEVEL -DF_MALLOC -DUSE_LOCAL_ROUTE -DSVNREVISION='"2:5135M"' -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_EPOLL -DHAVE_SIGIO_RT -DHAVE_SELECT -c checks.c -o checks.o [...] When I try to start the proxy it complains about: CRITICAL:core:yyerror: parse error in config file, line 432, column 1-2: syntax error CRITICAL:core:yyerror: parse error in config file, line 432, column 1-2: invalid local_route statement As you announced this feature for OpenSER 1.4 release series, I assume this is available for kamailio v1.4.2 ? Best regards, Pascal ---------- Forwarded message ---------- From: Pascal Maugeri <pascal.maugeri(a)gmail.com> Date: Wed, Oct 29, 2008 at 11:17 AM Subject: How to enable local_route feature ? To: Henning Westerholt <henning.westerholt(a)1und1.de> Cc: devel(a)lists.openser.org, openser users <users(a)lists.openser.org> Hi Following your instructions I have enable the compilation defined in Makefile.defs and recompile everything after a make clean. One capture of the compilation for you to see the define is enable: [...] gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-stringops -falign-loops -ftree-vectorize -mtune=prescott -Wold-style-definition -Wmissing-field-initializers -Wredundant-decls -DMOD_NAME='"uri_db"' -DNAME='"kamailio"' -DVERSION='"1.4.2-notls"' -DARCH='"i386"' -DOS='"linux"' -DCOMPILER='"gcc 4.0.2"' -D__CPU_i386 -D__OS_linux -D__SMP_yes -DCFG_DIR='"/usr/local/etc/kamailio/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DSTATISTICS -DCHANGEABLE_DEBUG_LEVEL -DF_MALLOC -DUSE_LOCAL_ROUTE -DSVNREVISION='"2:5135M"' -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_EPOLL -DHAVE_SIGIO_RT -DHAVE_SELECT -c checks.c -o checks.o [...] When I try to start the proxy it complains about: CRITICAL:core:yyerror: parse error in config file, line 432, column 1-2: syntax error CRITICAL:core:yyerror: parse error in config file, line 432, column 1-2: invalid local_route statement As you announced this feature for OpenSER 1.4 release series, I assume this is available for kamailio v1.4.2 ? Best regards, Pascal On Thu, Jun 26, 2008 at 1:11 PM, Henning Westerholt < henning.westerholt(a)1und1.de> wrote: > On Friday 06 June 2008, Bogdan-Andrei Iancu wrote: > > OpenSER has a new type of route: local route. This route is to be > > executed when a brand new request is internally generated (openser being > > the UAC) ; such requests are result of : > > - t_uac_dlg MI command > > - msilo, sms, presence, cpl-c, dialog (and others) modules > > [..] > > Hello all, > > the addition of this feature short before the code freeze caused some > conflicts, which could not resolved sufficently in time for this release. > Thus the OpenSER board was asked to decide in this matter. The majority of > the board voted for decativating this feature in the 1.4 release series. > > For more details please take a look at the developer mailing list at [1], > [2] > and [3]. Details about the "dectivate" commit can be found at [4] > > The local route functionality is still available, but its not activated in > the > default installation. In order to use this feature its necessary to set > the "USE_LOCAL_ROUTE" define in the "Makefile.defs" file and compile your > own > binary from the source. Then it will possible to use this feature. > > In the 1.5.0 release this functionality (or something resemble this) will > be > present, fully usable and supported. > > With best regards, > > Henning Westerholt > > > [1] http://lists.openser.org/pipermail/devel/2008-June/014028.html > [2] http://lists.openser.org/pipermail/devel/2008-June/014122.html > [3] http://lists.openser.org/pipermail/devel/2008-June/014204.html > [4] http://lists.openser.org/pipermail/devel/2008-June/014444.html > > > -- > Henning Westerholt - Development Consumer Products / DSL Core > 1&1 Internet AG, Ernst-Frey-Str. 9, 76135 Karlsruhe, Germany > > _______________________________________________ > Users mailing list > Users(a)lists.openser.org > http://lists.openser.org/cgi-bin/mailman/listinfo/users >

2 1

[Kamailio-Users] Kamailio/Openser - improve the performance with children process
by Daniel Cardoso Alves 29 Oct '08

29 Oct '08

Hi people... Is there a number of children that the Kamailio/Openser for improve the performance? Each process takes care of a request? Thanks in advance. Novos endereços, o Yahoo! que você conhece. Crie um email novo com a sua cara @ymail.com ou @rocketmail.com. http://br.new.mail.yahoo.com/addresses

3 2

Re: [Kamailio-Users] I don't have asterisk audio to openser - mediaproxy
by luzango mfupe 29 Oct '08

29 Oct '08

Hi Ricky,Where is your Kamailio config?? is this your full ngrep capture?? Rgds, Luzango. > > Message: 2 > Date: Tue, 28 Oct 2008 23:10:12 -0700 (PDT) > From: Ricky Gutierrez <xserverlinux(a)yahoo.com> > Subject: [Kamailio-Users] I don't have asterisk audio to openser - > mediaproxy > To: users(a)lists.kamailio.org > Message-ID: <654712.75990.qm(a)web59903.mail.ac4.yahoo.com> > Content-Type: text/plain; charset="us-ascii" > > Hi list is making tests with openser 1.3.2 and mediaproxy to solve the nat, > I have gotten myself an ip it public with my supplier, I have two network > cards in the pc that I am using for openser and mediaproxy together with > asterisk, making tests with mediaproxy 1.9.1 when I receive a call from the > pstn through asterisk I don't have audio, if I call to the pstn they listen > to me well . > > > From: "Ventas" <sip:112@192.168.10.1 <sip%3A112(a)192.168.10.1> > >;tag=69451218021829df > To: <sip:2685249@192.168.10.1 <sip%3A2685249(a)192.168.10.1> > >;tag=329cfeaa6ded039da25ff8cbb8668bd2.b1b2 > Contact: <sip:112@192.168.10.30:5060;transport=udp> > Supported: path > Call-ID: fb5f5dac83056f72(a)192.168.10.30 > CSeq: 7492 ACK > User-Agent: Grandstream GXP2020 1.1.6.16 > Max-Forwards: 70 > Allow: > INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE > Content-Length: 0 > > > # > U +0.022110 192.168.10.30:5060 -> 192.168.10.1:5060 > INVITE sip:2685249@192.168.10.1 <sip%3A2685249(a)192.168.10.1> SIP/2.0 > Via: SIP/2.0/UDP 192.168.10.30:5060;branch=z9hG4bKf428b928c25dad03 > From: "Ventas" <sip:112@192.168.10.1 <sip%3A112(a)192.168.10.1> > >;tag=69451218021829df > To: <sip:2685249@192.168.10.1 <sip%3A2685249(a)192.168.10.1>> > Contact: <sip:112@192.168.10.30:5060;transport=udp> > Supported: replaces, timer, path > Proxy-Authorization: Digest username="112", realm="192.168.10.1", > algorithm=MD5, uri="sip:2685249@192.168.10.1 <sip%3A2685249(a)192.168.10.1>", > nonce="4907ac8cb6dc757eb6ba5522e0fdb9786b4c3d6e", > response="c40a9387fdf5de29115c1edadc7f79db" > Call-ID: fb5f5dac83056f72(a)192.168.10.30 > CSeq: 7493 INVITE > User-Agent: Grandstream GXP2020 1.1.6.16 > Max-Forwards: 70 > Allow: > INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE > Content-Type: application/sdp > Content-Length: 358 > > v=0 > o=112 8000 8001 IN IP4 192.168.10.30 > s=SIP Call > c=IN IP4 192.168.10.30 > t=0 0 > m=audio 5004 RTP/AVP 0 18 3 97 2 9 101 > a=sendrecv > a=rtpmap:0 PCMU/8000 > a=rtpmap:18 G729/8000 > a=rtpmap:3 GSM/8000 > a=rtpmap:97 iLBC/8000 > a=fmtp:97 mode=20 > a=rtpmap:2 G726-32/8000 > a=rtpmap:9 G722/16000 > a=ptime:20 > a=rtpmap:101 telephone-event/8000 > a=fmtp:101 0-11 > > # > U +0.003938 192.168.10.1:5060 -> 192.168.10.30:5060 > SIP/2.0 100 Giving a try > Via: SIP/2.0/UDP 192.168.10.30:5060 > ;branch=z9hG4bKf428b928c25dad03;rport=5060 > From: "Ventas" <sip:112@192.168.10.1 <sip%3A112(a)192.168.10.1> > >;tag=69451218021829df > To: <sip:2685249@192.168.10.1 <sip%3A2685249(a)192.168.10.1>> > Call-ID: fb5f5dac83056f72(a)192.168.10.30 > CSeq: 7493 INVITE > Server: OpenSER (1.3.2-notls (i386/linux)) > Content-Length: 0 > > > # > U +0.000115 192.168.10.1:5060 -> 192.168.10.1:5070 > INVITE sip:2685249@192.168.10.1:5070 SIP/2.0 > Record-Route: <sip:192.168.10.1;lr=on;ftag=69451218021829df;nat=yes> > Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK400f.b93e5c35.0 > Via: SIP/2.0/UDP 192.168.10.30:5060 > ;rport=5060;branch=z9hG4bKf428b928c25dad03 > From: "Ventas" <sip:112@192.168.10.1 <sip%3A112(a)192.168.10.1> > >;tag=69451218021829df > To: <sip:2685249@192.168.10.1 <sip%3A2685249(a)192.168.10.1>> > Contact: <sip:112@192.168.10.30:5060;transport=udp> > Supported: replaces, timer, path > Call-ID: fb5f5dac83056f72(a)192.168.10.30 > CSeq: 7493 INVITE > User-Agent: Grandstream GXP2020 1.1.6.16 > Max-Forwards: 69 > Allow: > INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE > Content-Type: application/sdp > Content-Length: 358 > P-hint: route(3)|setflag7,forcerport,fix_contact > P-hint: inbound->inbound > P-hint: Route[6]: mediaproxy > > v=0 > o=112 8000 8001 IN IP4 192.168.10.30 > s=SIP Call > c=IN IP4 192.168.1.64 > t=0 0 > m=audio 35040 RTP/AVP 0 18 3 97 2 9 101 > a=sendrecv > a=rtpmap:0 PCMU/8000 > a=rtpmap:18 G729/8000 > a=rtpmap:3 GSM/8000 > a=rtpmap:97 iLBC/8000 > a=fmtp:97 mode=20 > a=rtpmap:2 G726-32/8000 > a=rtpmap:9 G722/16000 > a=ptime:20 > a=rtpmap:101 telephone-event/8000 > a=fmtp:101 0-11 > > # > U +0.000471 192.168.10.1:5070 -> 192.168.10.1:5060 > SIP/2.0 100 Trying > Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK400f.b93e5c35.0;received= > 192.168.10.1 > Via: SIP/2.0/UDP 192.168.10.30:5060 > ;rport=5060;branch=z9hG4bKf428b928c25dad03 > Record-Route: <sip:192.168.10.1;lr=on;ftag=69451218021829df;nat=yes> > From: "Ventas" <sip:112@192.168.10.1 <sip%3A112(a)192.168.10.1> > >;tag=69451218021829df > To: <sip:2685249@192.168.10.1 <sip%3A2685249(a)192.168.10.1>> > Call-ID: fb5f5dac83056f72(a)192.168.10.30 > CSeq: 7493 INVITE > User-Agent: Asterisk PBX > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY > Supported: replaces > Contact: <sip:2685249@192.168.10.1:5070> > Content-Length: 0 > > > I don't have a lot of experience with mediaproxy, and I have some doubts > that such you see they can help me to clarify, inside the file > mediaproxy.ini some options appear which I have configured them but I am not > sure if it is the best way. > > my scenario is the following one: > > <-> UAC<-> NAT <-> ADSL <-> Internet <-> > eth0 wan (public ip x.x.x.x ) <- openser/mediaproxy/asterisk -> eth1 lan ( > 192.168.11.1) <-> UAC > > > [MediaProxy] > > start = yes > socket = /var/run/mediaproxy.sock > group = openser > listen = None > allow = None > proxyIP = x.x.x.x (public ip) > ;portRange = 60000:65000 > portRange = 35000:65000 > TOS = 0xb8 > idleTimeout = 60 > holdTimeout = 3600 > forceClose = 0 > > [Accounting] > ; one of none, radius or database > accounting = none > > [Database] > user = dbuser > password = dbpass > host = dbhost > database = radius > table = radacct > > [Radius] > secret = secret > server = localhost > authport = 1812 > acctport = 1813 > dictionaries = /etc/radiusclient-ng/dictionary, > /etc/openser/radius/dictionary, /usr/share/mediaproxy/dictionary > retries = 2 > timeout = 3 > > > > > this couple of you line inside the openser, I don't still understand them > according to the guide of ser getting started they are for asymmetric > clients, but I don't find an example > > modparam("mediaproxy","sip_asymmetrics","/etc/openser/sip-clients") > modparam("mediaproxy","rtp_asymmetrics","/ect/openser/rtp-clients") > > somebody that can give me a good help... > > regards > > rickygm > > > > -- Luzango Mfupe TUUNE MOBILE Tel:0128440528/0123825710 Tshwane-RSA "...Ships are safe in harbor, but they were never meant to stay there......."

1 0

[Kamailio-Users] Fwd: Re: How to enable local_route feature ?
by Henning Westerholt 29 Oct '08

29 Oct '08

On Wednesday 29 October 2008, Pascal Maugeri wrote: (you can reach the kamailio list at lists.kamailio.org, the lists at openser.org goes to the opensips lists) > Following your instructions I have enable the compilation defined in > Makefile.defs and recompile everything after a make clean. One capture of > the compilation for you to see the define is enable: > > [...] > gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -Wall > -minline-all-stringops -falign-loops -ftree-vectorize -mtune=prescott > -DF_MALLOC -DUSE_LOCAL_ROUTE -DSVNREVISION='"2:5135M"' -DFAST_LOCK > [..] > checks.c -o checks.o > [...] > > When I try to start the proxy it complains about: > > CRITICAL:core:yyerror: parse error in config file, line 432, column 1-2: > syntax error > CRITICAL:core:yyerror: parse error in config file, line 432, column 1-2: > invalid local_route statement > > As you announced this feature for OpenSER 1.4 release series, I assume this > is available for kamailio v1.4.2 ? Hi Pascal, i just tried it with the trunk (which should show the same behaviour with regards to this feature). My compilation accepts local_route { [..] } in the configuration. Can you quote the relevant part of your configuration? Cheers, Henning

1 0

[Serusers] Error logs for SER
by Shruti Sanadhya 29 Oct '08

29 Oct '08

Hi, I am trying to setup a SER on Ubuntu 8.04 (Hardy heron). I have been following the starter's guide for configuring my SER but I do not know where to look for the error logs. I just get a 'bad config file' error. Where can I get more details? Thanks

2 1

Jump to page:

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