[Freeswitch-users] blocking 183 w/o sdp

[Steven Ayre]

Close. You can only have one set of {} brackets. You can separate multiple
variables with a comma.

<action application="bridge"
data="{sip_contact_user=${contact},sip_ignore_183nosdp=true}sofia/sbc/$1@
${dialed_domain}"/>

-Steve


On 29 January 2011 04:29, Sam <u2nsam at gmail.com> wrote:

> Hi,
>
> So you say i need to put
> <action application="bridge"
> data="{sip_contact_user=${contact}}{sip_ignore_183nosdp=true}sofia/sbc/$1@
> ${dialed_domain}"/>
>
> Regds
> Sam
>
>
>
>
>
> On Fri, Jan 28, 2011 at 10:23 PM, Anthony Minessale <
> anthony.minessale at gmail.com> wrote:
>
>> you need sip_ignore_183nosdp=true set on the b leg not the a leg.
>> Put it in the dial string in {}
>>
>> {sip_ignore_183nosdp=true}sofia/foo/foo at bar.com
>>
>>
>> On Fri, Jan 28, 2011 at 12:41 AM, Sam <u2nsam at gmail.com> wrote:
>> > Hi,
>> >
>> > how can i ignore 183 without sdp,
>> > what happens is the provider sends 183 without sdp and by applying
>> "<action
>> > application="set" data="sip_ignore_183nosdp=true"/>"  the FS sends 180
>> to
>> > the leg a.
>> > Here i want to block the 183 with SDP just like router as b2bua and send
>> > nothing to leg a, and when actual 183 with sdp comes it should send .
>> >
>> > Its because, providers are sending false signaling by sending 183
>> without
>> > sdp,and it hampers while @ production,
>> > Although by cisco sbc i have done this but i want to do it by FS,
>> > Take a scenario, when call is send 183 without sdp for 10 secs and then
>> > followed by 183 with sdp ( actual signal),
>> > but when some one dials invalid number it rings for 10 secs and then
>> gives
>> > SIP cause 404, which is bad from the providers.
>> > So this is the reason i want to block it.
>> >
>> > Most of the providers do this, the way out is blocking.
>> >
>> > I have got an advice from Tihomir  to do "execute_on_ring and parse your
>> 180
>> > / 183 messages in search of SDP,
>> > once you get 183 without SDP do not send it back to leg a and send
>> signal
>> > only when you got 183 with sdp or 180 "
>> > And this could be valid call flow.
>> >
>> > This happens in many cases where the provider is having nextone as a sbc
>> and
>> > that too tier 1 !
>> >
>> > Regards
>> > Sam
>> >
>> > _______________________________________________
>> > 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>
>> googletalk:conf+888 at conference.freeswitch.org<googletalk%3Aconf%2B888 at conference.freeswitch.org>
>> pstn:+19193869900
>>
>> _______________________________________________
>> 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/20110129/a606532b/attachment.html