Re: [Freeswitch-users] outgoing callerid freetdm TDM400
That looks like the problem I had with my FXS ports sending CID not understood by european phones. In which country are you / what kind of analog phones are you using ? François On Wed, 8 Sep 2010 13:16:08 +1000, Brian May <brian@microcomaustralia.com.au> wrote:
On 8 September 2010 11:21, Moises Silva <moises.silva@gmail.com> wrote:
Pastebin a debug log for a call. Also, before placing the call, create the directory /var/log/freetdm and then execute this in FreeSWITCH CLI: ftdm trace /var/log/freetdm/test <span> <chan>
Hopefully I got this right ;-)
<http://pastebin.com/dEXkkNaK>
To me everything looks good in this listing.
Not sure what I can do with the freetdm trace files...
On 8 September 2010 17:36, François Legal <devel@thom.fr.eu.org> wrote:
In which country are you / what kind of analog phones are you using ?
Australia, using an Australian phone. I have set the Australian operating mode for the drivers too, from dmesg: [ 18.101882] Boosting ringer on slot 1 (89V peak) [ 18.102608] Module 0: Installed -- AUTO FXS/DPO [ 18.985083] Boosting ringer on slot 2 (89V peak) [ 18.986770] Module 1: Installed -- AUTO FXS/DPO [ 19.188100] Module 2: Installed -- AUTO FXO (AUSTRALIA mode) [ 19.389066] Module 3: Installed -- AUTO FXO (AUSTRALIA mode) [ 19.390928] Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules) -- Brian May <brian@microcomaustralia.com.au>
Well, there seem to be a specific standard for Australia. You should maybe dig about how CID is supposed to be signaled in this standard. Here in France, CID has to be sent before the first ring pulse, or between first and second ring pulse. I made a patch for freetdm and this works for me. I did make an update to latest trunk a month ago, and the patch could be almost successfully applied. It should be attached to JIRA OPENZAP-100. François On Wed, 8 Sep 2010 18:38:58 +1000, Brian May <brian@microcomaustralia.com.au> wrote:
On 8 September 2010 17:36, François Legal <devel@thom.fr.eu.org> wrote:
In which country are you / what kind of analog phones are you using ?
Australia, using an Australian phone.
I have set the Australian operating mode for the drivers too, from dmesg:
[ 18.101882] Boosting ringer on slot 1 (89V peak) [ 18.102608] Module 0: Installed -- AUTO FXS/DPO [ 18.985083] Boosting ringer on slot 2 (89V peak) [ 18.986770] Module 1: Installed -- AUTO FXS/DPO [ 19.188100] Module 2: Installed -- AUTO FXO (AUSTRALIA mode) [ 19.389066] Module 3: Installed -- AUTO FXO (AUSTRALIA mode) [ 19.390928] Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules)
On 8 September 2010 19:11, François Legal <devel@thom.fr.eu.org> wrote:
Well, there seem to be a specific standard for Australia. You should maybe dig about how CID is supposed to be signaled in this standard. Here in France, CID has to be sent before the first ring pulse, or between first and second ring pulse. I made a patch for freetdm and this works for me.
Hmmm. You might be on to something here. It wouldn't surprise me at all if out standards are similar to France. Unfortunately having problems finding anything more definite then this, except for pages for Asterisk that say I have to change: sendcalleridafter=1 to sendcalleridafter=2 <http://www.voip-info.org/wiki/view/Australia+Asterisk+Details>
I did make an update to latest trunk a month ago, and the patch could be almost successfully applied. It should be attached to JIRA OPENZAP-100.
What do you mean by "JIRA OPENZAP-100"? I have updated to the latest Freeswitch Trunk, not sure if you mean your patch has been included or not. -- Brian May <brian@microcomaustralia.com.au>
No, it's not included. The patch is attached to this JIRA bug report. Go to jira.freeswitch.org, then find the freetdm section, and look for open/in progress issues. You'll find one which is tagged OPENZAP-100. Then inside this one, there is a file patch-mwi1.txt attached. It should be the one to go. Patch your freetdm source tree with this file, then rebuild mod_freetdm and install the lib in your freeswitch setup. You then have to add the lines modem_type = FSK_V23_FORWARD_MODE1 (or the modulation type that best fits your setup) in freetdm.conf, and you should be good to go. Or at least try. François On Wed, 8 Sep 2010 19:49:12 +1000, Brian May <brian@microcomaustralia.com.au> wrote:
On 8 September 2010 19:11, François Legal <devel@thom.fr.eu.org> wrote:
Well, there seem to be a specific standard for Australia. You should maybe dig about how CID is supposed to be signaled in this standard. Here in France, CID has to be sent before the first ring pulse, or between first and second ring pulse. I made a patch for freetdm and this works for me.
Hmmm. You might be on to something here. It wouldn't surprise me at all if out standards are similar to France.
Unfortunately having problems finding anything more definite then this, except for pages for Asterisk that say I have to change:
sendcalleridafter=1
to
sendcalleridafter=2
<http://www.voip-info.org/wiki/view/Australia+Asterisk+Details>
I did make an update to latest trunk a month ago, and the patch could be almost successfully applied. It should be attached to JIRA OPENZAP-100.
What do you mean by "JIRA OPENZAP-100"?
I have updated to the latest Freeswitch Trunk, not sure if you mean your patch has been included or not.
On 8 September 2010 20:45, François Legal <devel@thom.fr.eu.org> wrote:
No, it's not included. The patch is attached to this JIRA bug report. Go to jira.freeswitch.org, then find the freetdm section, and look for open/in progress issues. You'll find one which is tagged OPENZAP-100. Then inside this one, there is a file patch-mwi1.txt attached. It should be the one to go. Patch your freetdm source tree with this file, then rebuild mod_freetdm and install the lib in your freeswitch setup. You then have to add the lines modem_type = FSK_V23_FORWARD_MODE1 (or the modulation type that best fits your setup) in freetdm.conf, and you should be good to go. Or at least try.
Doesn't seem to apply cleanly :-( patching file libs/freetdm/mod_freetdm/mod_freetdm.c Hunk #1 succeeded at 133 (offset 12 lines). Hunk #2 succeeded at 2193 (offset 167 lines). Hunk #3 succeeded at 3699 (offset 429 lines). Hunk #4 FAILED at 3589. Hunk #5 succeeded at 4055 (offset 431 lines). Hunk #6 succeeded at 4090 (offset 431 lines). Hunk #7 succeeded at 4274 (offset 431 lines). Hunk #8 succeeded at 4301 (offset 431 lines). 1 out of 8 hunks FAILED -- saving rejects to file libs/freetdm/mod_freetdm/mod_freetdm.c.rej patching file libs/freetdm/src/ftdm_io.c Hunk #1 succeeded at 969 (offset 39 lines). Hunk #2 succeeded at 1251 (offset 22 lines). Hunk #3 succeeded at 2688 (offset 163 lines). Hunk #4 succeeded at 2721 (offset 163 lines). Hunk #5 succeeded at 3291 (offset 272 lines). Hunk #6 succeeded at 3336 (offset 272 lines). Hunk #7 succeeded at 3779 (offset 323 lines). Hunk #8 succeeded at 3913 (offset 323 lines). patching file libs/freetdm/src/ftdm_threadmutex.c patching file libs/freetdm/src/ftmod/ftmod_analog/ftmod_analog.c Hunk #2 succeeded at 337 (offset 1 line). Hunk #3 succeeded at 402 (offset 1 line). Hunk #4 succeeded at 426 (offset 1 line). Hunk #5 succeeded at 443 (offset 1 line). Hunk #6 succeeded at 477 (offset 1 line). Hunk #7 succeeded at 493 (offset 1 line). Hunk #8 succeeded at 548 (offset 1 line). Hunk #9 succeeded at 673 (offset 1 line). Hunk #10 succeeded at 680 (offset 1 line). Hunk #11 succeeded at 692 (offset 1 line). patching file libs/freetdm/src/include/freetdm.h Hunk #1 succeeded at 435 (offset 10 lines). patching file libs/freetdm/src/include/private/ftdm_core.h Hunk #1 succeeded at 432 (offset 20 lines). patching file libs/freetdm/src/include/private/ftdm_types.h Hunk #3 succeeded at 224 (offset 24 lines). patching file src/mod/applications/mod_voicemail/mod_voicemail.c Hunk #2 succeeded at 1444 with fuzz 2 (offset 8 lines). Hunk #3 succeeded at 1673 (offset 9 lines). Hunk #4 succeeded at 1693 (offset 9 lines). Hunk #5 succeeded at 1727 (offset 9 lines). Hunk #6 succeeded at 1905 (offset 9 lines). Hunk #7 succeeded at 2197 (offset 9 lines). Hunk #8 succeeded at 2336 (offset 9 lines). Hunk #9 succeeded at 2412 (offset 9 lines). Hunk #10 succeeded at 2478 (offset 9 lines). Hunk #11 FAILED at 3631. Hunk #12 succeeded at 3663 (offset 15 lines). Hunk #13 succeeded at 4022 (offset 15 lines). Hunk #14 succeeded at 4068 (offset 15 lines). Hunk #15 succeeded at 4107 (offset 15 lines). Hunk #16 succeeded at 4167 (offset 15 lines). Hunk #17 succeeded at 4229 (offset 15 lines). Hunk #18 succeeded at 4276 (offset 15 lines). 1 out of 18 hunks FAILED -- saving rejects to file src/mod/applications/mod_voicemail/mod_voicemail.c.rej -- Brian May <brian@microcomaustralia.com.au>
On Wed, 8 Sep 2010 20:58:11 +1000, Brian May <brian@microcomaustralia.com.au> wrote:
On 8 September 2010 20:45, François Legal <devel@thom.fr.eu.org> wrote:
No, it's not included. The patch is attached to this JIRA bug report. Go to jira.freeswitch.org, then find the freetdm section, and look for open/in progress issues. You'll find one which is tagged OPENZAP-100. Then inside this one, there is a file patch-mwi1.txt attached. It should be the one to go. Patch your freetdm source tree with this file, then rebuild mod_freetdm and install the lib in your freeswitch setup. You then have to add the lines modem_type = FSK_V23_FORWARD_MODE1 (or the modulation type that best fits your setup) in freetdm.conf, and you should be good to go. Or at least try.
Doesn't seem to apply cleanly :-(
I know I should not say that ..., but this should not be a problem. This patch does a lot of things to freetdm (it also contains the MWI feature for analog phones, plus a modification in mod_voicemail to allow message notifications be sent to freetdm (look at JIRA OPENZAP-101 for information on how this work). Anyway, it should be worth a try like this. François
I know I should not say that ..., but this should not be a problem. This patch does a lot of things to freetdm (it also contains the MWI feature for analog phones, plus a modification in mod_voicemail to allow message notifications be sent to freetdm (look at JIRA OPENZAP-101 for information on how this work).
Anyway, it should be worth a try like this.
It would be better if you can update the patch. I will be back at looking at analog next week, so it's your chance to get your functionality included. Moises Silva Senior Software Engineer Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com
Then I'll manage to have this done. Could you also please take a look at "[Freeswitch-users] problem trying to make analog calls from freetdm channel to another freetdm channel" topic. It is a problem I kind of had when upgrading to latest trunk befoe providing my latest patch for remote hangup detection (OPENZAP-123). It seems the FTDM_CHANNEL_OUTBOUND never get set when creating an outbound channel of analog type. François On Wed, 8 Sep 2010 10:18:33 -0400, Moises Silva wrote: I know I should not say that ..., but this should not be a problem. This patch does a lot of things to freetdm (it also contains the MWI feature for analog phones, plus a modification in mod_voicemail to allow message notifications be sent to freetdm (look at JIRA OPENZAP-101 for information on how this work). Anyway, it should be worth a try like this. It would be better if you can update the patch. I will be back at looking at analog next week, so it's your chance to get your functionality included. Moises Silva Senior Software Engineer Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com [1] Links: ------ [1] mailto:moy@sangoma.com
Yes, plz try again and let me know if you find anything else. Particularly for analog we need all the help we can get with testing since we mostly focus on PRI and SS7. Moises Silva Senior Software Engineer Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com On Wed, Sep 8, 2010 at 10:41 AM, François Legal <devel@thom.fr.eu.org>wrote:
Then I'll manage to have this done.
Could you also please take a look at "[Freeswitch-users] problem trying to make analog calls from freetdm channel to another freetdm channel" topic.
It is a problem I kind of had when upgrading to latest trunk befoe providing my latest patch for remote hangup detection (OPENZAP-123).
It seems the FTDM_CHANNEL_OUTBOUND never get set when creating an outbound channel of analog type.
François
On Wed, 8 Sep 2010 10:18:33 -0400, Moises Silva <moises.silva@gmail.com> wrote:
I know I should not say that ..., but this should not be a problem.
This patch does a lot of things to freetdm (it also contains the MWI feature for analog phones, plus a modification in mod_voicemail to allow message notifications be sent to freetdm (look at JIRA OPENZAP-101 for information on how this work).
Anyway, it should be worth a try like this.
It would be better if you can update the patch. I will be back at looking at analog next week, so it's your chance to get your functionality included.
Moises Silva Senior Software Engineer Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
It seems to be working now -- thanks for the quick response. Moises Silva <moises.silva@gmail.com> wrote:
Yes, plz try again and let me know if you find anything else. Particularly for analog we need all the help we can get with testing since we mostly focus on PRI and SS7.
Moises Silva Senior Software Engineer Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com
On Wed, Sep 8, 2010 at 10:41 AM, François Legal <devel@thom.fr.eu.org>wrote:
Then I'll manage to have this done.
Could you also please take a look at "[Freeswitch-users] problem trying to make analog calls from freetdm channel to another freetdm channel" topic.
It is a problem I kind of had when upgrading to latest trunk befoe providing my latest patch for remote hangup detection (OPENZAP-123).
It seems the FTDM_CHANNEL_OUTBOUND never get set when creating an outbound channel of analog type.
François
On Wed, 8 Sep 2010 10:18:33 -0400, Moises Silva <moises.silva@gmail.com> wrote:
I know I should not say that ..., but this should not be a problem.
This patch does a lot of things to freetdm (it also contains the MWI feature for analog phones, plus a modification in mod_voicemail to allow message notifications be sent to freetdm (look at JIRA OPENZAP-101 for information on how this work).
Anyway, it should be worth a try like this.
It would be better if you can update the patch. I will be back at looking at analog next week, so it's your chance to get your functionality included.
Moises Silva Senior Software Engineer Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
---------------------------------------------------- Alternatives:
---------------------------------------------------- _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com
This works for me too. I have updated the CID patch against today's git. The patch now contains only the CID part. I created a separate MWI patch that I attached to OPENZAP-101. François On Wed, 8 Sep 2010 11:38:03 -0400, Moises Silva wrote: Yes, plz try again and let me know if you find anything else. Particularly for analog we need all the help we can get with testing since we mostly focus on PRI and SS7. Moises Silva Senior Software Engineer Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com [1] On Wed, Sep 8, 2010 at 10:41 AM, François Legal wrote: Then I'll manage to have this done. Could you also please take a look at "[Freeswitch-users] problem trying to make analog calls from freetdm channel to another freetdm channel" topic. It is a problem I kind of had when upgrading to latest trunk befoe providing my latest patch for remote hangup detection (OPENZAP-123). It seems the FTDM_CHANNEL_OUTBOUND never get set when creating an outbound channel of analog type. François On Wed, 8 Sep 2010 10:18:33 -0400, Moises Silva wrote: I know I should not say that ..., but this should not be a problem. This patch does a lot of things to freetdm (it also contains the MWI feature for analog phones, plus a modification in mod_voicemail to allow message notifications be sent to freetdm (look at JIRA OPENZAP-101 for information on how this work). Anyway, it should be worth a try like this. It would be better if you can update the patch. I will be back at looking at analog next week, so it's your chance to get your functionality included. Moises Silva Senior Software Engineer Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com [4] _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org [5] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users [6] UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users [7] http://www.freeswitch.org [8] Links: ------ [1] mailto:moy@sangoma.com [2] mailto:devel@thom.fr.eu.org [3] mailto:moises.silva@gmail.com [4] mailto:moy@sangoma.com [5] mailto:FreeSWITCH-users@lists.freeswitch.org [6] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users [7] http://lists.freeswitch.org/mailman/options/freeswitch-users [8] http://www.freeswitch.org
On 9 September 2010 18:54, François Legal <devel@thom.fr.eu.org> wrote:
I have updated the CID patch against today's git. The patch now contains only the CID part. I created a separate MWI patch that I attached to OPENZAP-101.
Wow! It seems to work. I get caller id again. Not sure what modem_type I got, I skipped that step ;-). So it is possible it may not be adhere with Australian standards, it works with my phone though, so I am happy. Now if only I could get the analogue phone's flash function to work ;-). -- Brian May <brian@microcomaustralia.com.au>
On Thu, 9 Sep 2010 21:03:10 +1000, Brian May <brian@microcomaustralia.com.au> wrote:
On 9 September 2010 18:54, François Legal <devel@thom.fr.eu.org> wrote:
I have updated the CID patch against today's git. The patch now contains only the CID part. I created a separate MWI patch that I attached to OPENZAP-101.
Wow! It seems to work. I get caller id again.
Not sure what modem_type I got, I skipped that step ;-). So it is possible it may not be adhere with Australian standards, it works with my phone though, so I am happy.
Now if only I could get the analogue phone's flash function to work ;-).
Glad to hear that. By what I saw while trying, it seems the modem type does not so much make a difference (analog phones seem to be tolerant to both BELL and V23). What do you call the flash function ? François
On Thu, Sep 9, 2010 at 8:15 AM, François Legal <devel@thom.fr.eu.org> wrote:
On Thu, 9 Sep 2010 21:03:10 +1000, Brian May <brian@microcomaustralia.com.au> wrote:
On 9 September 2010 18:54, François Legal <devel@thom.fr.eu.org> wrote:
I have updated the CID patch against today's git. The patch now contains only the CID part. I created a separate MWI patch that I attached to OPENZAP-101.
Wow! It seems to work. I get caller id again.
Not sure what modem_type I got, I skipped that step ;-). So it is possible it may not be adhere with Australian standards, it works with my phone though, so I am happy.
Now if only I could get the analogue phone's flash function to work ;-).
Glad to hear that.
By what I saw while trying, it seems the modem type does not so much make a difference (analog phones seem to be tolerant to both BELL and V23).
What do you call the flash function ?
on-hook/off-hook done quickly. Brian, what is it that does not work with flash? Moises Silva Senior Software Engineer Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com
On 9 September 2010 21:03, Brian May <brian@microcomaustralia.com.au> wrote:
On 9 September 2010 18:54, François Legal <devel@thom.fr.eu.org> wrote:
I have updated the CID patch against today's git. The patch now contains only the CID part. I created a separate MWI patch that I attached to OPENZAP-101.
Wow! It seems to work. I get caller id again.
Is there any progress in getting these changes incorporated into the official git repository? Looks like when I updated to the latest git version I broken callerid :-(. Unfortunately the patch in OPENZAP-100 no longer applies cleanly either. http://jira.freeswitch.org/browse/OPENZAP-100 -- Brian May <brian@microcomaustralia.com.au>
On 9 September 2010 00:41, François Legal <devel@thom.fr.eu.org> wrote:
It is a problem I kind of had when upgrading to latest trunk befoe providing my latest patch for remote hangup detection (OPENZAP-123).
I can't seem to find a OPENZAP-123 bug... -- Brian May <brian@microcomaustralia.com.au>
On 8 September 2010 21:16, François Legal <devel@thom.fr.eu.org> wrote:
I know I should not say that ..., but this should not be a problem. This patch does a lot of things to freetdm (it also contains the MWI feature for analog phones, plus a modification in mod_voicemail to allow message notifications be sent to freetdm (look at JIRA OPENZAP-101 for information on how this work).
What is the minimum I need to patch just to get callerid working? Other stuff like MWI is nice, but until it gets integrated into git, I just want to test caller id for now. -- Brian May <brian@microcomaustralia.com.au>
On Thu, 9 Sep 2010 11:17:31 +1000, Brian May <brian@microcomaustralia.com.au> wrote:
On 8 September 2010 21:16, François Legal <devel@thom.fr.eu.org> wrote:
I know I should not say that ..., but this should not be a problem. This patch does a lot of things to freetdm (it also contains the MWI feature for analog phones, plus a modification in mod_voicemail to allow message notifications be sent to freetdm (look at JIRA OPENZAP-101 for information on how this work).
What is the minimum I need to patch just to get callerid working?
Other stuff like MWI is nice, but until it gets integrated into git, I just want to test caller id for now.
I understand that, but unfortunately, these are features I use, so when using git diff, I get all the modifications that I made. That implies having the MWI feature, and the remote hangup detection. Anyway, the patch you applied should just work for CID. The rejected hunks are either cosmetic (the first one) either you'll miss an MWI event sent to freetdm in one case. This should however not prevent you from building freetdm, and trying the CID feature. As I told Moises, I'm trying to update to latest git to provide a patch to the up to date freetdm. If I have some time, I'll try to make separate patch files for each feature. François
participants (4)
-
Brian May
-
covici＠ccs.covici.com
-
François Legal
-
Moises Silva