[Freeswitch-users] mod_opal - call charged before H.225 connect

Tue Oct 6 16:41:13 PDT 2009

Diego,

what i'm pointing here is the situation where you have a great product that
lacks in one of most common protocol. It is true H323 is going to disappear
(eventually), it is true that the community prefers SIP/IAX instead ... but
the reality still remains. H323 is going to be used for quite a long time to
exchange a lot of traffic while FS will be left aside. Today, when you setup
an IP peering interconnection 80% of carriers will prefer H323.

Of course, developing something costs "time" (and we all know what time
stands for...) and as i said, i understand the financial point of view and i
really understand if nobody is going to work on that, but let's face it FS
doesn't have any usable module to reliably handle H323 protocol.

said that, i don't intend to offend anyone... just facing the reality.

regarding the h323 module, we don't have any issue fixing the existing or
developing a new one... but before we go developing something it is always
better check if the thing you want already exists in an usable state or
not... that's what i did today.

So, I'm interested in a reliable module handling H323v4... anyone else?

T.

On Tue, Oct 6, 2009 at 11:45 PM, Diego Viola <diego.viola at gmail.com> wrote:

> Instead of complaining and demanding things for free, people should start
> to put their money where their mouth is.
>
> Diego
>
>
> On Tue, Oct 6, 2009 at 8:47 PM, Tihomir Culjaga <tculjaga at gmail.com>wrote:
>
>> hi Anthony,
>>
>> it is somewhere here:
>>
>>          switch_status_t
>> FSConnection::receive_message(switch_core_session_message_t *msg)
>>
>>
>> anyhow, i will open an issue jira of course.
>>
>>
>> I understand your financial point of view, but anyhow while the entire
>> world is wants sip and trying to move to sip, the reality is quite
>> different. The majority of voice traffic exchanged via IP is still H323.
>> This means a working SIP - H323 interworking is really needed... pity nobody
>> wants/has time to work in this direction to produce a decent mod_h323.
>>
>>
>>
>> T.
>>
>>
>>
>>
>>
>>
>> On Tue, Oct 6, 2009 at 9:25 PM, Anthony Minessale <
>> anthony.minessale at gmail.com> wrote:
>>
>>> pcap is not as useful as FS console log on debug with:
>>> sofia profile internal siptrace on
>>>
>>> you should be reporting issues to jira under mod_opal not to the mailing
>>> list.
>>> http://jira.freeswitch.org
>>>
>>> FYI
>>> There is little financial support from the community for h323 which
>>> prevents the mod_opal from getting much attention.
>>> We actually have to contract the author of opal to help with these issues
>>> including the original writing of the module that he did with very little
>>> funding and nobody ever wants to pay him to improve it.
>>>
>>> That does not mean your issue will not be addressed but there is no
>>> promise how fast it will be.
>>>
>>>
>>>
>>> On Tue, Oct 6, 2009 at 12:37 PM, Tihomir Culjaga <tculjaga at gmail.com>wrote:
>>>
>>>> hello guys,
>>>>
>>>>
>>>> i was playing with mod_opal to see if i can make it working ... well it
>>>> seems SIP-H323 interworking is not tuned at all.
>>>>
>>>> I have a call from a registered sip user (1001) to PSTN via mod_opal
>>>>
>>>>
>>>> <include>
>>>>   <extension name="EMERGENCY">
>>>>     <condition field="destination_number"
>>>> expression="^0(112|9[23456])$">
>>>>       <action application="set"
>>>> data="effective_caller_id_number=1001282122"/>
>>>>       <action application="set" data="NCX_IP=10.4.4.254"/>
>>>>       <action application="set" data="call_timeout=30"/>
>>>>       <action application="set" data="hangup_after_bridge=true"/>
>>>>
>>>>       <action application="bridge" data="opal/h323:0$1@${NCX_IP}"/>
>>>>     </condition>
>>>>   </extension>
>>>>
>>>>   <extension name="SPECIAL_SERVICES">
>>>>     <condition field="destination_number"
>>>> expression="^0(9[01789]\d{3,4})$">
>>>>       <action application="set"
>>>> data="effective_caller_id_number=1001282122"/>
>>>>       <action application="set" data="NCX_IP=10.4.4.254"/>
>>>>       <action application="set" data="call_timeout=30"/>
>>>>       <action application="set" data="hangup_after_bridge=true"/>
>>>>
>>>>       <action application="bridge" data="opal/h323:0$1@${NCX_IP}"/>
>>>>     </condition>
>>>>   </extension>
>>>>
>>>>   <extension name="ENYTHING_ELSE">
>>>>     <condition field="destination_number"
>>>> expression="^0([2-8]\d{6,7}|0[1-9]\d{7,8}|00[1-9]\d{8,16})$">
>>>>       <action application="set"
>>>> data="effective_caller_id_number=1001282122"/>
>>>>       <action application="set" data="NCX_IP=10.4.4.254"/>
>>>>       <action application="set" data="call_timeout=30"/>
>>>>       <action application="set" data="hangup_after_bridge=true"/>
>>>>
>>>>       <action application="bridge" data="opal/h323:0$1@${NCX_IP}"/>
>>>>     </condition>
>>>>   </extension>
>>>> </include>
>>>>
>>>>
>>>>
>>>> One of the many issues i sow is that FS connects the call on SIP leg
>>>> before it actually receives H.225 connect from H323 leg... as it is
>>>> configured to send 200 OK on the 1st H.225 message containing a FastStart
>>>> element/OLC.
>>>>
>>>>
>>>> Attached is the tcpdump i took on FS machine... just use this filter:
>>>> "h225 or h245 or q931 or sip"
>>>> Also, you can check the attac CDR,,,, this is an unanswered call i
>>>> placed to PSTN and FS billed it 23 seconds.
>>>>
>>>>
>>>>
>>>> Can anyone tell where i can do correct SIP - H323 message mappings to
>>>> avoid this?
>>>>
>>>>
>>>>
>>>> T.
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> FreeSWITCH-users mailing list
>>>> FreeSWITCH-users at lists.freeswitch.org
>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>> UNSUBSCRIBE:
>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>> http://www.freeswitch.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Anthony Minessale II
>>>
>>> FreeSWITCH http://www.freeswitch.org/
>>> ClueCon http://www.cluecon.com/
>>> Twitter: http://twitter.com/FreeSWITCH_wire
>>>
>>> AIM: anthm
>>> MSN:anthony_minessale at hotmail.com <MSN%3Aanthony_minessale at hotmail.com>
>>> GTALK/JABBER/PAYPAL:anthony.minessale at gmail.com<PAYPAL%3Aanthony.minessale at gmail.com>
>>> IRC: irc.freenode.net #freeswitch
>>>
>>> FreeSWITCH Developer Conference
>>> sip:888 at conference.freeswitch.org <sip%3A888 at conference.freeswitch.org>
>>> iax:guest at conference.freeswitch.org/888
>>> googletalk:conf+888 at conference.freeswitch.org<googletalk%3Aconf%2B888 at conference.freeswitch.org>
>>> pstn:213-799-1400
>>>
>>> _______________________________________________
>>> FreeSWITCH-users mailing list
>>> FreeSWITCH-users at lists.freeswitch.org
>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>>> http://www.freeswitch.org
>>>
>>>
>>
>> _______________________________________________
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>>
>>
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20091007/22cb2195/attachment-0002.html 