November 2010 - FreeSWITCH-users - FreeSWITCH Mailing Lists

Does FreeTDM provides RDNIS to FreeSwitch
by lakshmanan ganapathy 16 Nov '10

16 Nov '10

Hi all, I've just tried the FreeTDM module with the libsng. It seems that I'm not getting the redirection number. A called to B. B is redirected to C. In the SETUP packet I got "redirection number" as B. But in FreeSwitch, I've not got the "redirection number". I also wanted to know whether the stack ( libsng ), itself not providing the RDNIS or FreeTDM is not updating it? Please help!

5 8

Latency on Google Voice (GTalk)
by mazilo 16 Nov '10

16 Nov '10

I have followed this http://wiki.freeswitch.org/wiki/Google_Voice Google Voice Wiki HOWTO to configure my FS v1.0.6 (hosted on an inexpensive Seagate http://www.seagate.com/www/en-us/products/network_storage/freeagent_dockstar DockStar running on an OpenWRT Linux). My FS has no problem to process outbound/inbound calls. The only problem I have noticed is the audio from B-leg (the audio from the party I conversed to) has about 1.5s latency. I wonder if anyone has noticed this. If anyone out here knows how to fix this, please kindly chime in. FYI, here is my jingle_profiles/gtalk_client.xml file: <profile type="client"> @gmail.com/gtalk"/> </profile> ----- don't and stop are the ONLY two 4-letter words considered offensive to men, but not when used together. -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Latency-on-Google-Voice-GTalk… Sent from the freeswitch-users mailing list archive at Nabble.com.

3 4

problem registering with sip providers
by dnb＠bluewin.ch 16 Nov '10

16 Nov '10

hello, i'm running FreeSWITCH Version 1.0.head (svn-18355) on vmware behind nat. i have problems registering with sip providers: 2010-11-12 13:20:28.845507 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:20:34.866728 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:20:38.898868 [WARNING] sofia_reg.c:387 iptel Failed Registration, setting retry to 30 seconds. 2010-11-12 13:20:40.902922 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:20:46.953148 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:20:52.974365 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:20:58.998596 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:04.025773 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:09.049973 [NOTICE] sofia_reg.c:342 Registering iptel 2010-11-12 13:21:10.051987 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:16.081210 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:22.106424 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:28.150642 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:34.216910 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:40.281096 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:40.281096 [WARNING] sofia_reg.c:387 iptel Failed Registration, setting retry to 30 seconds. 2010-11-12 13:21:46.297302 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:52.318592 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:58.379775 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:22:04.411977 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:22:10.426183 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:22:11.430227 [NOTICE] sofia_reg.c:342 Registering iptel 2010-11-12 13:22:16.441404 [NOTICE] sofia_reg.c:342 Registering sipcall after a while sipcall still gets registered, im able to receive inbound calls, but i cant get outbound working. iptel doesn't get registered at all, for that i followed the instruction in the FreeSWITCH-106- Book i bought. can someone please give me a hint. thanks

2 1

Problem registering with sip providers
by Tom Wendel 16 Nov '10

16 Nov '10

hello, i'm running FreeSWITCH Version 1.0.head (svn-18355) on vmware behind nat. i have problems registering with sip providers: 2010-11-12 13:20:28.845507 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:20:34.866728 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:20:38.898868 [WARNING] sofia_reg.c:387 iptel Failed Registration, setting retry to 30 seconds. 2010-11-12 13:20:40.902922 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:20:46.953148 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:20:52.974365 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:20:58.998596 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:04.025773 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:09.049973 [NOTICE] sofia_reg.c:342 Registering iptel 2010-11-12 13:21:10.051987 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:16.081210 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:22.106424 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:28.150642 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:34.216910 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:40.281096 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:40.281096 [WARNING] sofia_reg.c:387 iptel Failed Registration, setting retry to 30 seconds. 2010-11-12 13:21:46.297302 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:52.318592 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:58.379775 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:22:04.411977 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:22:10.426183 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:22:11.430227 [NOTICE] sofia_reg.c:342 Registering iptel 2010-11-12 13:22:16.441404 [NOTICE] sofia_reg.c:342 Registering sipcall after a while sipcall still gets registered, im able to receive inbound calls, but i cant get outbound working. iptel doesn't get registered at all, for that i followed the instruction in the FreeSWITCH-106- Book i bought. can someone please give me a hint. thanks

2 1

Sangoma FreeTDM Warnings in freeswitch log
by Stephen Wilde 16 Nov '10

16 Nov '10

Hi, I have a freeswitch log full of warnings from sangoma isdn stack with message "Invalid PCB state". There is a way to investigate on this warning? I'm using latest freeswitch release from git. Thanks, Stephen LOG: 2010-11-15 16:13:21.127384 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:21.346458 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:22.281442 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:22.579400 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:23.220464 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:23.944729 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:24.112472 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:24.384740 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:24.480446 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:24.823447 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:25.123583 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:25.344967 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:26.286484 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:26.350443 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:26.447604 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:26.576444 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:26.873428 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:27.216449 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:27.827803 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:28.387918 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:28.478494 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:28.814442 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:29.147749 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:30.352525 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:30.451471 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:30.716466 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:30.872475 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:31.420568 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:31.451476 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:31.832502 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:32.815483 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265) 2010-11-15 16:13:33.146510 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:753 [SNGISDN Q931] s16: Internal: Unknown Event Code(5): Invalid PCB state(265)

3 3

Video Support
by Samuel Macedo 15 Nov '10

15 Nov '10

Hi, I've already read that FS supports video, but I've never seen anyone using or talking about how to use it. Does FS support video conferences? Or only video calls? Is there any documentation about this subject? Thanks, -- Samuel Macedo

5 9

(no subject)
by Will Smith 15 Nov '10

15 Nov '10

2 2

call forward question
by Tihomir Culjaga 15 Nov '10

15 Nov '10

hello, its just a stupid question ... but how do we handle network call forward in FS ? usually you we can activate call forward on the terminal itself and when a call hits the terminal it responds with a 302 message. This works but not with an unplugged terminal. So, is there any way to do a call network forward? Meaning if extension 1000 activates a CFU (by dialing some FAC - e.g. *21*<number>) to 1002 and we have an incoming call to 1000, FS should place the call to 1002 without even going to look at extension 1000. any chance without a mambo-jumbo hacking? T.

2 2

problem registering with sip providers
by dnb＠bluewin.ch 15 Nov '10

15 Nov '10

hello, i'm running FreeSWITCH Version 1.0.head (svn-18355) on vmware behind nat. i have problems registering with sip providers: 2010-11-12 13:20:28.845507 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:20:34.866728 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:20:38.898868 [WARNING] sofia_reg.c:387 iptel Failed Registration, setting retry to 30 seconds. 2010-11-12 13:20:40.902922 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:20:46.953148 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:20:52.974365 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:20:58.998596 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:04.025773 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:09.049973 [NOTICE] sofia_reg.c:342 Registering iptel 2010-11-12 13:21:10.051987 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:16.081210 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:22.106424 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:28.150642 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:34.216910 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:40.281096 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:40.281096 [WARNING] sofia_reg.c:387 iptel Failed Registration, setting retry to 30 seconds. 2010-11-12 13:21:46.297302 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:21:52.318592 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:21:58.379775 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:22:04.411977 [NOTICE] sofia_reg.c:342 Registering sipcall 2010-11-12 13:22:10.426183 [WARNING] sofia_reg.c:387 sipcall Failed Registration, setting retry to 5 seconds. 2010-11-12 13:22:11.430227 [NOTICE] sofia_reg.c:342 Registering iptel 2010-11-12 13:22:16.441404 [NOTICE] sofia_reg.c:342 Registering sipcall after a while sipcall still gets registered, im able to receive inbound calls, but i cant get outbound working. iptel doesn't get registered at all, for that i followed the instruction in the FreeSWITCH-106- Book i bought. can someone please give me a hint. thanks

1 0

Bad sound with crackle
by Loïc 15 Nov '10

15 Nov '10

Hello, I am a new user of FreeSwitch and I try to switch from Asterisk to FreeSwitch. For now, I just registered a SIP line and I made an extension in the dialplan to playback music on hold when I call : <context name="default"> <extension name="test"> <condition>  <action application="answer"/> <action application="playback" data="$${hold_music}"/> </condition> </extension> </context> When I call I have a problem with the sound, it is very bad, I hear very fast crackle. On the console I can see a warning during my call and that's all: 2010-11-12 13:02:45.119517 [NOTICE] switch_channel.c:784 New Channel sofia/external/anonymous(a)anonymous.invalid [c27034e2-ee54-11df-ad91-7fc19b304698] 2010-11-12 13:02:45.122548 [INFO] mod_dialplan_xml.c:331 Processing Anonymous <anonymous>->test in context default 2010-11-12 13:02:45.125555 [NOTICE] mod_dptools.c:920 Channel [sofia/external/anonymous(a)anonymous.invalid] has been answered 2010-11-12 13:02:45.508790 [WARNING] mod_sofia.c:1036 Asynchronous PTIME not supported, changing our end from 30 to 20 If I add <X-PRE-PROCESS cmd="set" data="timer_name=soft"/> in vars.xml, when I call the sound is good but I still get the warning : 2010-11-12 13:05:42.789161 [NOTICE] switch_channel.c:784 New Channel sofia/external/anonymous(a)anonymous.invalid [2c565760-ee55-11df-a0d9-0f91e325cd76] 2010-11-12 13:05:42.791179 [INFO] mod_dialplan_xml.c:331 Processing Anonymous <anonymous>->test in context default 2010-11-12 13:05:42.794179 [NOTICE] mod_dptools.c:920 Channel [sofia/external/anonymous(a)anonymous.invalid] has been answered 2010-11-12 13:05:43.174443 [WARNING] mod_sofia.c:1036 Asynchronous PTIME not supported, changing our end from 30 to 20 2010-11-12 13:05:43.175461 [INFO] sofia.c:709 sofia/external/anonymous(a)anonymous.invalid Update Callee ID to "anonymous" <anonymous> Is this normal? Why should I add this line in vars.xml for it to work ? What does this warning? How to solve it? Thank you in advance for your help. Loïc

5 6