Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: mod_gsmopen
-
Labels:None
-
Platform:Linux x86/gcc
-
CPU Info:
-
FreeSWITCH GIT Revision:FreeSWITCH Version 1.1.beta1 (git-893d7ef 2012-04-25 11-22-03 +0200)
-
Reproduced with GIT HEAD?:yes
Description
The setup is quite simple: e171 connected to PBX, Yealink T26 also as 1000 extension.
mod_gsmopen.conf.xml
<configuration name="gsmopen.conf" description="GSMopen Configuration">
<global_settings>
<param name="debug" value="8"/>
<param name="dialplan" value="XML"/>
<param name="context" value="default"/>
<param name="hold-music" value="$${moh_uri}"/>
<param name="destination" value="9198"/>
</global_settings>
<!-- one entry here per gsmopen interface -->
<per_interface_settings>
<interface id="1" name="gsm01">
<param name="controldevice_name" value="/dev/ttyUSB2"/>
<param name="controldevice_audio_name" value="/dev/ttyUSB1"/>
<param name="context" value="default"/>
<param name="hold-music" value="$${moh_uri}"/>
<param name="destination" value="1000"/>
<!-- in windowz would be, eg: -->
<!--
<param name="controldevice_name" value="COM4"/>
-->
<!-- 3G PC UI Interface is controldevice_name -->
<!--
<param name="controldevice_audio_name" value="COM2"/>
-->
<!-- 3G Application Interface is controldevice_audio_name -->
</interface>
<!-- following interfaces are commented out!
-->
</per_interface_settings>
</configuration>
Just bridge to 1000 extension @ default context. But actually when my Yealink is ringing I must hit my answer button twise to accept the call. Judging by the complete logs of the call (http://pastebin.freeswitch.com/18924) 1000 extension proceeds twice @ default context after getting ORIGINATOR_CANCEL (why?).
Logs: http://pastebin.freeswitch.com/18924
Thus I think that this bug is releated to some another strange issue (I will report it lately) when bridging to another FS (acting like GSM-VOIP gateway).
mod_gsmopen.conf.xml
<configuration name="gsmopen.conf" description="GSMopen Configuration">
<global_settings>
<param name="debug" value="8"/>
<param name="dialplan" value="XML"/>
<param name="context" value="default"/>
<param name="hold-music" value="$${moh_uri}"/>
<param name="destination" value="9198"/>
</global_settings>
<!-- one entry here per gsmopen interface -->
<per_interface_settings>
<interface id="1" name="gsm01">
<param name="controldevice_name" value="/dev/ttyUSB2"/>
<param name="controldevice_audio_name" value="/dev/ttyUSB1"/>
<param name="context" value="default"/>
<param name="hold-music" value="$${moh_uri}"/>
<param name="destination" value="1000"/>
<!-- in windowz would be, eg: -->
<!--
<param name="controldevice_name" value="COM4"/>
-->
<!-- 3G PC UI Interface is controldevice_name -->
<!--
<param name="controldevice_audio_name" value="COM2"/>
-->
<!-- 3G Application Interface is controldevice_audio_name -->
</interface>
<!-- following interfaces are commented out!
-->
</per_interface_settings>
</configuration>
Just bridge to 1000 extension @ default context. But actually when my Yealink is ringing I must hit my answer button twise to accept the call. Judging by the complete logs of the call (http://pastebin.freeswitch.com/18924) 1000 extension proceeds twice @ default context after getting ORIGINATOR_CANCEL (why?).
Logs: http://pastebin.freeswitch.com/18924
Thus I think that this bug is releated to some another strange issue (I will report it lately) when bridging to another FS (acting like GSM-VOIP gateway).
Author: Giovanni Maruzzelli <gmaruzz@gmail.com>
Date: Thu May 3 10:56:37 2012 +0200
gsmopen: fix
FS-4150, deleted a spurious new_inbound_channel(), checked all gsmopen->fs->sip machinery, then I got problems with audio(only in gsmopen->fs->sip not the reverse): I was baffled by a snom bug for a week, then I tested with Xlite and worked, so I grow suspicious, I updated snom320 firmware and worked. Hate those things