Talk:Mod lcr
From FreeSWITCH Wiki
Discuss:
Known issue with lcr cli
lcr on a number that is an exact match to a digits entry in the lcr table will use 100% cpu. Don't do it until fixed.
should support more than just sofia (sip)
We should support more than just sofia as an endpoint. Perhaps modifying carrier_gateway to be a bit more generic would do.
add fields prefix, suffix remove fields gateway, term_host, port
then we'd build the dial string as
switch_mprintf("%s%s%s%s%s", cur_route->gw_prefix, cur_route->prefix, destination_number, cur_route->suffix, cur_route->gw_suffix
to use gateway routing
prefix = sofia/gateway/gatewayname/
suffix = (nothing)</br>
would result in
sofia/gateway/gatewayname/number
to use host routing
prefix = sofia/${use_profile}/
suffix = @host:port
would result in
sofia/${use_profile}/number@host:port
I think this would be more flexible than the current setup.
both above implemented
[intra] - if I don't see you on irc, I have a patch for both of these implemented...
-rupa
Manipulate caller ID based on carrier.
Carriers expect different caller ID formats and it should be possible to manipulate it, just like with the prefix/destination.
-Inspired
Manipulate called number (CLD/DN) in To: header based on carrier
Does it make sense to be able to do manipulations of the To: header as well as the From: header (callerID)? Thinking of an inter-op SBC type scenario where specific carriers/interconnects require INVITE/To/From/P-ID to be in specific formats, perhaps where all of those fields are converted to E.164 when the come into FreeSWITCH, then converted to the carriers-specific format on outbound.
-cupis
The rate and carrier.id should be set as channel variables
This enables us to do calculations of costs and profits at a later time as the data is already stored in the CDR record.
-Inspired
Full Freeswitch SBC
Need help with a write up..
I expanded on what you created with lcr to create an SBC.
I need help with testing and tweeking. I added easyroute for inbound but not sure if this is the best way..
http://wiki.freeswitch.org/wiki/Advance_SBC_with_mod_lcr_and_mod_easyroute
Prefix Matching Question
Maybe I'm missing something, but here's my situation: I have one carrier with rates for each NPA/NXX. I have another carrier with a flat rate for all domestic US calls. So, for example, on the number 1-434-392-xxxx, Carrier A has a digit match of 1434392 with a rate of 0.02151, and Carrier B has a Digit Match of 1 with a rate of 0.01390. mod_lcr appears to be preferring Carrier A because of the better digit match. Is this expected behavior, and does anyone have any suggestions as to what I should do in order to get the cheaper carrier in this case? Am I just misunderstanding this somehow? Thanks!
--You can use reorder_by_rate. Beware though - "1" includes Bahamas and other non-USA locales that are $0.20+ so make sure your carrier has an entry for those also, or it will show .0139 even for those areas. Avi Marcus
