date:20140201

Re: [SR-Users] Media-proxy Query

2014-02-01 Thread Nandini madhu

Dear All,

Anybody please help me in resolving this issue.

Awaiting somebody's suggestions.

Regards,
Nandini


On Wed, Jan 29, 2014 at 4:18 PM, Nandini madhu  wrote:

> Dear All,
> Greetings,
>
> I have configured Kamailio (4.0.3) with mediaproxy server, with this
> set-up audio/video calls are going good and hence NAT issue has solved.
> I have used two soft clients: 1) IMSDroid 2) Bria.
> But i have a query about media-proxy statistics i.e in the syslog, the
> info about media-proxy activity is shown as below:
>
> *Case 1*: when Call between two IMSDroid clients.
>
> caller_codec : 'Unknown(73)'
>
> callee_codec : 'Unknown(73)'
>
> callee_ua : 'unknown agent'.
>
> *Case 2* : When call between two Bria clients.
>
> 'callee_ua': 'unknown agent'.
>
> (Calls using Bria clients media-proxy's syslog shows Audio codec names,
> but using IMSdroid clients it is showing 'Unknown' for Audio codec names ).
>
> Find the attachment below for the full syslog about the mentioned unknown
> behaviour. And also find my kamailio.cfg file.
>
> And also logging in the syslog as shown like RTP: Unknown , RTCP: Unknown.
>
> In this context, there is a jitter in audio calls and pixelled video
> sometimes, So is there any wrong with the above mentioned "unknown' factor
> in this problem of jitter/pixelled audio/video calls ?
> (AFAIK these payload type 73 (i.e 72-76) is reserved for RTCP conflict
> avoidance. right? )
>
> What could be the problem for this 'Unknown' issue?
> How can i solve this issue ? Anything can be done in kamailio script?
> And how these RTCP payload types (72-76) plays a role in audio/video calls?
>
> Any suggestions will greatly help. please help me in clarifying these
> issues.
>
> Thanks in advance.
>
> Regards,
> Nandini
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] kamailio 4.1.1 failure routes issue

2014-02-01 Thread José Seabra

Hello there,

I think that i found a bug within failure routes on version 4.1.1, i have a
call flow that needs to use the failure routes 4 times if nobody answer the
call, but when the call goes to the 3º attempt to same failure route
kamailio doesn't handle the transaction,

With the same kamailio script but using the version 4.0.1 kamailio works
correctly.

Please check the attachment with kamailio debug level 3



-- 
Cumprimentos
José Seabra
free_result(): freeing result set at 0x7ffb54eba9a0
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG: registrar 
[lookup.c:158]: lookup(): '3...@admin.com' Not found in usrloc
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG:  
[forward.c:730]: update_sock_struct_from_via(): update_sock_struct_from_via: 
trying SRV lookup
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG:  
[msg_translator.c:204]: check_via_address(): check_via_address(10.0.20.2, 
10.0.20.2, 0)
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG: sl 
[sl_funcs.c:515]: sl_run_callbacks(): execute callback for event type 1
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG: siptrace 
[siptrace.c:1732]: pipport2su(): the port string is 5060
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG: siptrace 
[siptrace.c:1732]: pipport2su(): the port string is 5062
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG:  
[proxy.c:278]: mk_proxy(): DEBUG: mk_proxy: doing DNS lookup...
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG: tm 
[t_lookup.c:1071]: t_check_msg(): DEBUG: t_check_msg: msg id=3 global id=3 T 
start=0x7ffb46019a58
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG: tm 
[t_lookup.c:1143]: t_check_msg(): DEBUG: t_check_msg: T already found!
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG: tm 
[t_reply.c:1663]: cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR 
timers reset
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG:  
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list 
(nil)
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG:  
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list 
(nil)
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG:  
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list 
(nil)
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG:  
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list 
(nil)
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG:  
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list 
(nil)
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG:  
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list 
(nil)
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG:  
[xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil)
Feb  1 10:31:26 vx00-kml01 /usr/local/sbin/kamailio[5491]: DEBUG:  
[receive.c:296]: receive_msg(): receive_msg: cleaning up
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[parser/msg_parser.c:633]: parse_msg(): SIP Reply  (status):
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[parser/msg_parser.c:635]: parse_msg():  version: 
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[parser/msg_parser.c:637]: parse_msg():  status:  <480>
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[parser/msg_parser.c:639]: parse_msg():  reason:  
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[parser/parse_via.c:1284]: parse_via_param(): Found param type 232,  = 
; state=16
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[parser/parse_via.c:2672]: parse_via(): end of header reached, state=5
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=2
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[receive.c:152]: receive_msg(): After parse_msg...
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG: tm 
[t_lookup.c:1071]: t_check_msg(): DEBUG: t_check_msg: msg id=3 global id=2 T 
start=0x
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[parser/parse_via.c:1284]: parse_via_param(): Found param type 232,  = 
; state=16
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[parser/parse_via.c:2672]: parse_via(): end of header reached, state=5
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[5493]: DEBUG:  
[parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=62
Feb  1 10:31:27 vx00-kml01 /usr/local/sbin/kamailio[549

Re: [SR-Users] Kamailio without tls

2014-02-01 Thread Vitaliy Aleksandrov

Just add "listen=tcp:_kamailio_server_ip:5060" to the kamailio.cfg if 
don't have one and change sip settings of your SIP application to 
disable tls.
You can have both clear tcp and tls at the same time and application 
will choose which type of connection to use.


Hi Support,

I have recently kamailio 4.0.x version with tls on port 5061. Now our 
development team needs to connect to it using unencrypted on port 5060 
to test an app for features and then work towards connecting through 
tls connection.


So my question is how do I temporarily disable tls to test all the 
features on the kamailio server and then once feature testing is done 
revert back to tls connection?


Best Regards,

Neville D'Souza



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] dialog list query

2014-02-01 Thread John Murray

Hello,

 

I am managing calls with the dialog module in kamailio 4.0.4.

 

However if is try to get the callid and from_tag of existing calls using:

 

avp_db_query("select callid, from_tag from dialog", "$avp(s:s_callid),
$avp(s:s_from_tag)");

 

I get NULL, yet if I use:

 

sercmd proxy dlg.list

 

I get the calls listed correctly.

 

What am I doing wrong?

 

Thanks

 

John

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dialog list query

2014-02-01 Thread Charles Chance

John,

What db_mode are you using for dialog module? Are the entries in the db if
you check manually?

Are you able to fetch other data using avp_db_query? And do you see any
errors in the log?

Regards,

Charles
 On 1 Feb 2014 16:24, "John Murray"  wrote:

> Hello,
>
>
>
> I am managing calls with the dialog module in kamailio 4.0.4.
>
>
>
> However if is try to get the callid and from_tag of existing calls using:
>
>
>
> avp_db_query("select callid, from_tag from dialog", "$avp(s:s_callid),
> $avp(s:s_from_tag)");
>
>
>
> I get NULL, yet if I use:
>
>
>
> sercmd proxy dlg.list
>
>
>
> I get the calls listed correctly.
>
>
>
> What am I doing wrong?
>
>
>
> Thanks
>
>
>
> John
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>

-- 
www.sipcentric.com

Follow us on twitter @sipcentric 

Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered 
office: Unit 10 iBIC, Birmingham Science Park, Holt Court South, Birmingham 
B7 4EJ.
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] ngcp-mediaproxy-ng media address

2014-02-01 Thread Kelvin Chua

If you were to ask me, i would prefer that mp-ng would take the 2nd arg to
rtpproxy_manage and replace the sdp.

That way, it would be consistent to the behavior of the old one, rtpproxy.
On Feb 1, 2014 1:36 AM, "Richard Fuchs"  wrote:

> Hey,
>
> You're right, mediaproxy-ng is inconsistent with the docs. Just to
> clarify, when you call
>
> > rtpproxy_manage("co","10.17.0.102");
>
> you expect the new, rewritten SDP to come out with this IP address as
> media address in it, as opposed to the address(es) set on the MP-NG
> command line, right?
>
> Right now, MP-NG treats it as an override to the original address given
> in the received SDP. Not sure if it even makes sense to have that option.
>
> I'll push a fix shortly.
>
> cheers
>
>
> On 01/30/14 20:25, Kelvin Chua wrote:
> > somehow, mediaproxy is ignoring the media address set via
> >
> > rtpproxy_manage("co","10.17.0.102");
> >
> > anybody tried this before?
> >
> >
> > Jan 31 09:03:29 kam2 mediaproxy-ng[20455]: Got valid command from
> > 127.0.0.1:46077 : answer - { "sdp":
> > "v=0#015#012o=root 345956998 345956998 IN IP4
> > 10.17.0.105#015#012s=Asterisk PBX 11.7.0#015#012c=IN IP4
> > 10.17.0.105#015#012t=0 0#015#012m=audio 15712 RTP/AVP 97 3 0 8
> > 101#015#012a=rtpmap:97 speex/8000#015#012a=rtpmap:3
> > GSM/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8
> > PCMA/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101
> > 0-16#015#012a=ptime:20#015#012a=sendrecv#015#012", "replace": [
> > "session-connection", "origin" ], "call-id":
> > "yqtupxcwsnbmcbo@X340saucy", "received-from": [ "IP4", "10.17.0.105" ],
> > "media address": "22.9.18.15", "from-tag": "kjoel", "to-tag":
> > "as478f57f3", "command": "answer" }
> > Jan 31 09:03:29 kam2 mediaproxy-ng[20455]: Returning to SIP proxy:
> > d3:sdp541:v=0#015#012o=root 345956998 345956998 IN IP4
> > 10.17.0.102#015#012s=Asterisk PBX 11.7.0#015#012c=IN IP4
> > 10.17.0.102#015#012t=0 0#015#012a=ice-lite#015#012m=audio 10002 RTP/AVP
> > 97 3 0 8 101#015#012a=rtpmap:97 speex/8000#015#012a=rtpmap:3
> > GSM/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8
> > PCMA/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101
> >
> 0-16#015#012a=ptime:20#015#012a=sendrecv#015#012a=rtcp:10003#015#012a=ice-ufrag:QocOqhlR#015#012a=ice-pwd:HZ7WUgsHAKlLGp1n2FAzEwWsS9gj#015#012a=candidate:pMoXfVtH0dDfxpoa
> > 1 UDP 2130706432 10.17.0.102 10002 typ
> > host#015#012a=candidate:pMoXfVtH0dDfxpoa 2 UDP 2130706431 10.17.0.102
> > 10003 typ host#015#0126:result2:oke
> >
> >
> > Kelvin Chua
> >
> >
> > ___
> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> > sr-users@lists.sip-router.org
> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> >
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] ngcp-mediaproxy-ng media address

2014-02-01 Thread Richard Fuchs

The master branch on github already fixes that.

cheers


On 02/01/14 19:40, Kelvin Chua wrote:
> If you were to ask me, i would prefer that mp-ng would take the 2nd arg
> to rtpproxy_manage and replace the sdp.
> 
> That way, it would be consistent to the behavior of the old one, rtpproxy.
> 
> On Feb 1, 2014 1:36 AM, "Richard Fuchs"  > wrote:
> 
> Hey,
> 
> You're right, mediaproxy-ng is inconsistent with the docs. Just to
> clarify, when you call
> 
> > rtpproxy_manage("co","10.17.0.102");
> 
> you expect the new, rewritten SDP to come out with this IP address as
> media address in it, as opposed to the address(es) set on the MP-NG
> command line, right?
> 
> Right now, MP-NG treats it as an override to the original address given
> in the received SDP. Not sure if it even makes sense to have that
> option.
> 
> I'll push a fix shortly.
> 
> cheers
> 
> 
> On 01/30/14 20:25, Kelvin Chua wrote:
> > somehow, mediaproxy is ignoring the media address set via
> >
> > rtpproxy_manage("co","10.17.0.102");
> >
> > anybody tried this before?
> >
> >
> > Jan 31 09:03:29 kam2 mediaproxy-ng[20455]: Got valid command from
> > 127.0.0.1:46077  :
> answer - { "sdp":
> > "v=0#015#012o=root 345956998 345956998 IN IP4
> > 10.17.0.105#015#012s=Asterisk PBX 11.7.0#015#012c=IN IP4
> > 10.17.0.105#015#012t=0 0#015#012m=audio 15712 RTP/AVP 97 3 0 8
> > 101#015#012a=rtpmap:97 speex/8000#015#012a=rtpmap:3
> > GSM/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8
> > PCMA/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101
> > 0-16#015#012a=ptime:20#015#012a=sendrecv#015#012", "replace": [
> > "session-connection", "origin" ], "call-id":
> > "yqtupxcwsnbmcbo@X340saucy", "received-from": [ "IP4",
> "10.17.0.105" ],
> > "media address": "22.9.18.15", "from-tag": "kjoel", "to-tag":
> > "as478f57f3", "command": "answer" }
> > Jan 31 09:03:29 kam2 mediaproxy-ng[20455]: Returning to SIP proxy:
> > d3:sdp541:v=0#015#012o=root 345956998 345956998 IN IP4
> > 10.17.0.102#015#012s=Asterisk PBX 11.7.0#015#012c=IN IP4
> > 10.17.0.102#015#012t=0 0#015#012a=ice-lite#015#012m=audio 10002
> RTP/AVP
> > 97 3 0 8 101#015#012a=rtpmap:97 speex/8000#015#012a=rtpmap:3
> > GSM/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8
> > PCMA/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101
> >
> 
> 0-16#015#012a=ptime:20#015#012a=sendrecv#015#012a=rtcp:10003#015#012a=ice-ufrag:QocOqhlR#015#012a=ice-pwd:HZ7WUgsHAKlLGp1n2FAzEwWsS9gj#015#012a=candidate:pMoXfVtH0dDfxpoa
> > 1 UDP 2130706432 10.17.0.102 10002 typ
> > host#015#012a=candidate:pMoXfVtH0dDfxpoa 2 UDP 2130706431 10.17.0.102
> > 10003 typ host#015#0126:result2:oke
> >
> >
> > Kelvin Chua
> >
> >
> > ___
> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
> list
> > sr-users@lists.sip-router.org 
> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> >
> 
> 
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org 
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> 
> 
> 
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> 



signature.asc
Description: OpenPGP digital signature
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Packet loss / Jitter / Latency issues

2014-02-01 Thread Wingsravi R

Dear Daniel and Kamailio'ns

Greetings,

I am working on kamailio server (4.0.x),whicch is integreted with
media-proxy server (2.5.2) and it is all working fine in the point of SIP
functionality.

And i have a set-up like this below, with this when the calls (audio/video)
sessions started i am experiencing  latency,jitter, echo's in audio calls
and a choppy ,pixelled video :



KAMAILIO

|
Android SIP client (IMSDroid)  Wi-Fi
router  Switch (level 2)  Wi-Fi router  Android SIP client
(IMSDroid)

(Total set-up runs on Intranet infrastructure).

When i call between two SIP clients, Calls are getting established
successfully and RTP flow is also relaying using Media-proxy server. But
the audio/video performnce is not good enough. I am experiencing all this
Latency , jitter , Choppy pixelled video.

How can i resolve all this issues? What could be the problem ?

Ofcourse SIP proxy is not responsible all this problems (as i know ), But
is there anything  can be done on Media-proxy server ? Or anything Buffer
settings can be done on Kamailio server side (or anything else) ?
Even i changed Shared memory and Package memories to 512MB and 16MB
respectively.

Anybody can guess what may be the problems that causes these issues ?

PS: When i tried 'ping' Clients IP addresses in Kamailio server PC, there
is 20-30% packet loss also.

Please help me in resolving these issues.


Any help will greatly appreciate.

Regards,
Ravi.
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Media-proxy Query

[SR-Users] kamailio 4.1.1 failure routes issue

Re: [SR-Users] Kamailio without tls

[SR-Users] dialog list query

Re: [SR-Users] dialog list query

Re: [SR-Users] ngcp-mediaproxy-ng media address

Re: [SR-Users] ngcp-mediaproxy-ng media address

[SR-Users] Packet loss / Jitter / Latency issues

8 matches

Site Navigation

Mail list logo

Footer information