- FreeSWITCH-users - FreeSWITCH Mailing Lists

mod_nibblebill mp3
by Pete Kelly 26 Aug '11

26 Aug '11

Hi everyone I am looking at prepaid solutions at the moment, and mod_nibblebill seems pretty interesting. However the mp3 linked to from the wiki page is no longer available: http://wiki.freeswitch.org/wiki/Mod_nibblebill Does anyone have a copy at all? Also, how 'stable' is nibblebill, is it a well used module by people? I'll probably be starting off with large call volumes (rather than slow ramping up) so any ideas of usage statistics or advice on usage would be useful. Thanks Pete

1 0

Re: [Freeswitch-users] H264 packetization with echo app
by Dan-Cristian Bogos 26 Aug '11

26 Aug '11

Hey Anthony, Many thanks for so fast reaction. It works like a charm with your new patches. Have a good one! DanB

1 0

H264 packetization with echo app
by Dan-Cristian Bogos 25 Aug '11

25 Aug '11

Hey Guys, I have recently started playing with the echo application for video calls and found some possible issue (asking here if this is the desired behavior). Scenario: * Call gets connected with echo application, echoing audio just fine. * On reinvite the client sends the following SDP(please note the line with a=fmtp:102 packetization-mode=1): {{{ v=0. o=dan.test 0 1 IN IP4 10.10.10.106. s=-. c=IN IP4 10.10.10.106. t=0 0. m=audio 48576 RTP/AVP 9 96 97 0 8 98 100 5 6 15 101. a=rtpmap:9 G722/8000. a=rtpmap:96 speex/32000. a=rtpmap:97 speex/16000. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:98 iLBC/8000. a=rtpmap:100 speex/8000. a=rtpmap:5 DVI4/8000. a=rtpmap:6 DVI4/16000. a=rtpmap:15 G728/8000. a=rtpmap:101 telephone-event/8000. a=extmap:1 urn:ietf:params:rtp-hdrext:csrc-audio-level. m=video 55774 RTP/AVP 102 99. a=rtpmap:102 H264/90000. a=fmtp:102 packetization-mode=1. a=imageattr:102 send [x=[0-640],y=[0-480]] recv *. a=rtpmap:99 H264/90000. a=imageattr:99 send [x=[0-640],y=[0-480]] recv *. a=nortpproxy:yes. }}} * FreeSWITCH accepts it with 200 OK, returning the following SDP: {{{ v=0. o=Webi 1314226434 1314226435 IN IP4 10.10.10.106. s=Webi. c=IN IP4 127.0.0.1. t=0 0. m=audio 32256 RTP/AVP 9 101. a=rtpmap:9 G722/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=silenceSupp:off - - - -. a=ptime:20. m=video 18750 RTP/AVP 102. a=rtpmap:102 H264/90000. }}} Issue as seen by me: FreeSWITCH remaps the 102 from an offer with packetization=1 to a reply with packetization information missing, therefore defaulting to 0 (default out of RFC). Question: * Is this intentional or just some wrong negotiation of packetization parameter? Is FreeSWITCH not supporting packetization=1? Based on the negotiated stream the client should send now 102 with packetization=0 (as preferred by FreeSWITCH in signaling) and FreeSWITCH should return to the client 99 since 102 with packetization=1 does not look like being supported. My FreeSWITCH version is the latest git compiled yesterday: {{{ /opt/freeswitch/bin/freeswitch -version FreeSWITCH version: 1.0.head (git-8f15bc7 2011-08-23 14-40-44 -0500) }}} Thx in advance for any tip! DanB

2 1

about fax status
by Madovsky 25 Aug '11

25 Aug '11

Sometimes fax fails with status like Received a DCN while waiting for a DIS what does it mean ? Thanks Franck

2 1

Re: [Freeswitch-users] Forcing CN offer
by Alex Massover 25 Aug '11

25 Aug '11

Hi, Sorry, the RFC says that a= is not mandatory, m= is enough. I was just confused why FS in some scenario puts it and in other doesn’t, despite using only G711@8000. From: Alex Massover Sent: יום ה 25 אוגוסט 2011 12:26 To: 'freeswitch-users(a)lists.freeswitch.org' Subject: Forcing CN offer Hello, I’m working on the following scenarios: scenario 1: A --> FS --> B scenario 2: C --> FS --> A Where A supports CN (a=rtpmap:13 CN/8000) and requires CN negotiation, and B and C do not support and aren’t able to negotiate it. I successfully implemented scenario 1, CN is negotiated between A party and FS, and not negotiated between FS and B. But scenario 2 doesn’t work for me! When C doesn’t offer CN in INVITE towards FS, FS also doesn’t offer CN in SDP in INVITE towards A. And nothing helps, tried all the combination of VAD options. Gateway A is in the same internal sip profile in both scenarios. This is the SDP in INVITE from C to FS: Media Description, name and address (m): audio 30224 RTP/AVP 0 8 18 101 Media Attribute (a): rtpmap:0 PCMU/8000 Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute (a): rtpmap:18 G729/8000 Media Attribute (a): fmtp:18 annexb=no Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): fmtp:101 0-16 Media Attribute (a): silenceSupp:off - - - - Media Attribute (a): ptime:20 Media Attribute (a): sendrecv And this is the SDP from FS towards A: Media Description, name and address (m): audio 23564 RTP/AVP 0 8 101 13 Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): fmtp:101 0-16 Media Attribute (a): ptime:20 FS even puts 13 in m= attribute, but doesn’t add a= attribute for rtpmap:13. Is that a bug? -- Best Regards Alex Massover. This mail was sent via Mail-SeCure System.

1 0

Flex Client Receives Periodic Interrupted Audio
by afshin afzali 25 Aug '11

25 Aug '11

Hi Guys, As a taste of RTMP end point, I'm experiencing periodic interrupted audio. Everything is as defaults in client / server sides except that "auth-calls = false" and client does not login / logout, It just makes call. I don't know if it can justified by buffer-len / chunksize in server side or NetStream.bufferTime in client side. appreciate all comment. -- afshin

1 1

Paging with Polycom Phones
by Duvid Rottenberg 25 Aug '11

25 Aug '11

Has anyone successfully implemented paging (auto-answer) with a polycom phone? I am using the Conferencing and Intercom sample which sets the sip_auto_answer variable to true, however on my polycom phone the result is that the phone rings once and hangs up right away (the phone is sending a BYE message). I tried adding an Alert-Info header, however it seems that the Polycom format (Alert-Info: Ring Answer) isn't compliant with the RFC and I couldn't get freeswitch to send the header in this format. Has anyone else been able to either get polycom phones to work with sip_auto_answer or to get freeswitch to send an Alert-Info header in the polycom format? Thanks, Duvid Rottenberg

3 5

Options ping timer adjustment?
by Tim St. Pierre 24 Aug '11

24 Aug '11

Hello, Does anyone know of a way to adjust how often to send the options-ping packets? I really only need them to go about once every 30s, and it looks like they go every 10s or more. Thanks! -Tim

2 1

freeswitch crashed - gdb trace
by Leon de Rooij 24 Aug '11

24 Aug '11

Hi all, One of our FreeSWITCH servers crashed this morning. It happened when one of our customers suddenly started way more channels than usual (they went from about 100 to a little less than 500 channels). I have a core file and ran fscore_pb as suggested here: http://wiki.freeswitch.org/wiki/Debugging_Freeswitch#Simple_bash_script_to_… The output of that script was saved here: http://pastebin.freeswitch.org/17176 I'll spend all my free time to learn gdb, but for now can anyone help me find out what went wrong ? I'm a bit overwhelmed by the 16k lines that was generated by the script. Thanks & kind regards, Leon

1 0

Flowroute Users
by Brian West 24 Aug '11

24 Aug '11

https://support.flowroute.com/entries/20385652-inum-availability Please go voice your support! /b

1 0