[Freeswitch-users] FreeTDM, CallerID and Originate problems

Adam Voisey adam at voisey.me.uk
Tue Aug 12 22:39:15 MSD 2014


Hi,

I'm having a bit of trouble with FreeTDM, Sangoma Wanpipe and an A200
analogue card.  I was struggling getting caller ID to work for incoming
calls, but after asking the IRC channel it turned out to be my settings
were incorrect.  However upon correcting them, I've run into another
problem.

Short Issue: Caller ID is available but can't originate OR able to
originate but can't fetch caller ID.  Please see below for some
logs/settings.

CallerID on incoming calls is available when setting the following in
freetdm.conf.xml;

<param name="answer-polarity-reverse" value="true"/>
<param name="hangup-polarity-reverse" value="true"/>
<param name="polarity-callerid" value="true"/>

However, outbound originates such as "originate freetdm/FXO/a/078******53
&transfer(4000 XML default)" seem to "stick" at this point;

2014-08-12 19:04:59.470598 [DEBUG] ftdm_io.c:3976 [s1c1][1:1] Generating
DTMF [078******53]
2014-08-12 19:04:59.470598 [DEBUG] ftmod_wanpipe.c:938 [s1c1][1:1] First
packet write stats: Tx queue len: 1, Tx queue size: 5, Tx idle: 2661
2014-08-12 19:05:00.070585 [DEBUG] ftdm_io.c:3780 [s1c1][1:1] Queuing DTMF
0 (debug = 0)
2014-08-12 19:05:00.670577 [DEBUG] ftdm_io.c:3780 [s1c1][1:1] Queuing DTMF
8 (debug = 0)
2014-08-12 19:05:01.270587 [DEBUG] ftdm_io.c:3780 [s1c1][1:1] Queuing DTMF
4 (debug = 0)
2014-08-12 19:05:01.870631 [DEBUG] ftdm_io.c:3780 [s1c1][1:1] Queuing DTMF
3 (debug = 0)
2014-08-12 19:05:02.470593 [DEBUG] ftdm_io.c:3780 [s1c1][1:1] Queuing DTMF
5 (debug = 0)
2014-08-12 19:05:02.790593 [DEBUG] ftdm_io.c:3780 [s1c1][1:1] Queuing DTMF
3 (debug = 0)
2014-08-12 19:05:04.750618 [DEBUG] ftmod_analog.c:507 [s1c1][1:1] Changed
state from DIALING to PROGRESS_MEDIA
2014-08-12 19:05:04.770592 [DEBUG] ftmod_analog.c:638 [s1c1][1:1] Completed
state change from DIALING to PROGRESS_MEDIA in 20 ms
2014-08-12 19:05:04.770592 [DEBUG] ftmod_analog.c:644 [s1c1][1:1] Executing
state handler on 1:1 for PROGRESS_MEDIA

****** Phone B-Leg actually answered here ******

2014-08-12 19:05:57.010614 [NOTICE] switch_ivr_originate.c:3467 Hangup
FreeTDM/1:1/078******53 [CS_CONSUME_MEDIA] [NO_ANSWER]
2014-08-12 19:05:57.010614 [DEBUG] switch_channel.c:3222 Send signal
FreeTDM/1:1/078******53 [KILL]
2014-08-12 19:05:57.010614 [DEBUG] switch_core_session.c:1387 Send signal
FreeTDM/1:1/078******53 [BREAK]
2014-08-12 19:05:57.010614 [DEBUG] switch_core_state_machine.c:472
(FreeTDM/1:1/078******53) Running State Change CS_HANGUP
2014-08-12 19:05:57.010614 [DEBUG] switch_core_state_machine.c:735
(FreeTDM/1:1/078******53) Callstate Change DOWN -> HANGUP
2014-08-12 19:05:57.010614 [DEBUG] switch_core_state_machine.c:737
(FreeTDM/1:1/078******53) State HANGUP
2014-08-12 19:05:57.010614 [DEBUG] mod_freetdm.c:544 [1:1]
FreeTDM/1:1/078******53 CHANNEL HANGUP ENTER
2014-08-12 19:05:57.010614 [DEBUG] mod_freetdm.c:590 [s1c1][1:1] Changed
state from PROGRESS_MEDIA to HANGUP
2014-08-12 19:05:57.010614 [DEBUG] ftmod_analog.c:638 [s1c1][1:1] Completed
state change from PROGRESS_MEDIA to HANGUP in 4 ms
2014-08-12 19:05:57.010614 [DEBUG] ftmod_analog.c:644 [s1c1][1:1] Executing
state handler on 1:1 for HANGUP
2014-08-12 19:05:57.010614 [DEBUG] mod_freetdm.c:643 [1:1]
FreeTDM/1:1/078******53 CHANNEL HANGUP EXIT
2014-08-12 19:05:57.010614 [DEBUG] ftmod_wanpipe.c:982 [s1c1][1:1] Rx Queue
length exceeded 80% threshold (9/10)
2014-08-12 19:05:57.010614 [DEBUG] switch_core_state_machine.c:60
FreeTDM/1:1/078******53 Standard HANGUP, cause: NO_ANSWER

Eventually failing with a no-answer, even though it has been.
If I switch the polarity settings to false, then outbound calls work;

<param name="answer-polarity-reverse" value="false"/>
<param name="hangup-polarity-reverse" value="false"/>

However, I don't receive a Caller ID on inbound calls.  So I'm stuck
between either being able to originate calls but not getting an inbound ID
or receiving calls with an ID but not being able to originate.
Swapping the polairty options to true/false, false/true doesn't seem to
work either - although I thought it may be worth checking.
I'm in the UK using BT/Sky as my line provider who use V23 for sending the
CLI.

Any ideas?

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20140812/2887d18d/attachment.html 


Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users mailing list