[Freeswitch-users] More complex hunting question

ivdreg ivdreg ivdreg at gmail.com
Sun Oct 11 05:05:45 PDT 2009


Dear All,

I'm trying to use FS with xml_curl as routing server for otgoing calls to my
provides. Here is simplified setup:

[REGISTRARs] ----> [APP SERVERs] ----> [ROUTING SERVER/FreeSwitch] ---->
[SBC/no Transcoder]----> [Terminating GWs/ITSPs]

Because of simplicity I do not use hunting functionality in SBC but only in
FS.
I try to avoid if possible any trascoding but there are cases that it is
necessary. I want ROUTING SERVER to be
configured in proxy_media mode or bypass_media but on some errors such as
"415 Unsupported Media" that supposed are codec
negotiation issue to hunt again via trascoder before SBC.

Can someone help to find some elegant way functionality described below to
be achieved via dialplan_xml ?
Call to +XXXXXXXXXXXXXXXX for example:
available routes by priority are via: ITSP1,ITSP5,ITSP2,ITSP7
outgoing leg to ITSP1 - (returns unallocated number)
outgoing leg to ITSP5 - (returns "415 Unsupported Media")
    new outgoing leg to ITSP5 again but via transcoder - (If call is
connected OK, If other error hunt again to next GW - ITSP2)
outgoing leg to ITSP2 - (returns "415 Unsupported Media")
    new outgoing leg to ITSP2 again but via transcoder - (If call is
connected OK, If other error hunt again to next GW - ITSP7)
outgoing leg to ITSP7
Remarks: Codec errors may be more that one (415 Unsupported Media/488 Not
Acceptable Here ...) and number it ITSP/GW in not fixed.


Thanks to all.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20091011/41de3319/attachment-0002.html 


More information about the FreeSWITCH-users mailing list