2 Sep
2004
2 Sep
'04
2:53 p.m.
Yes, I understand that. I find the the idea of using timezones to create
the prefix interesting, other stuff can be more or less achieved using
generic rewrite rules. In my opinion it would be nice to have that
separated in some way, so that even users who do not need least cost
routing (like me) can use the code without the need to load all
additional stuff.
Jan.
On 02-09 13:13, Adrian Georgescu wrote:
E164 normalization I was referring into the document
to has (almost)
nothing to do with ENUM. It has to do with a consistent table with
destination prefixes in PSTN (country codes e.g. 49171 geman mobile/
network numbers to make it more clear). The destinations have names and
prices you might link to/from external systems. The normalization means
all PSTN calls will be brought to a normalized form according to E164
standard. If you dial extra 9 before pst numbers, local numbers without
country codes or not or you send to the gateway the country prefix or
add two zero is totally up to each configuration at each provider. LCR
makes sure it looks up the destination from one consistent table which
matches what Telco today are used to in building a dest/cost database.
Adrian
On Sep 2, 2004, at 12:32 PM, Jan Janak wrote:
One more thing, I like the E.164 normalization, I
would, however,
recommend to make it part of the enum module, instead of the LCR
module,
if you plan to contribute it into the main source tree, of course.
Jan.
On 02-09 11:18, Adrian Georgescu wrote:
>December 2004
>
>On Sep 2, 2004, at 6:31 AM, Atle Samuelsen wrote:
>
>>Howdy Adrian!
>>
>>Do you know when you whing you'll be finnish with this project? or
>>atleast ready for use?
>>
>>
>>-atle
>>
>>* Adrian Georgescu <ag(a)ag-projects.com> [040902 00:42]:
>>>There is some work in progress:
>>>
>>>http://download.dns-hosting.info/SERLCR/README
>>>
>>>Adrian
>>>
>>>>>>>>>>>
>>>Hi list,
>>>
>>>We have a setup with 2 redundant stateful SER SIP-Servers with
>>>accounting.
>>>
>>>For calls to the PSTN we have 2 ISDN-PRI gateways connected to
>>>different ISDN-PRI lines.
>>>
>>>We need to implement a dynamic failover mechanism and load
>>>balancing.
>>>
>>>a) Incoming calls: No problem, the PSTN switch takes care of that
>>>b) Outgoing calls:
>>> Both GWs are registered at both SERs; calls are usually relayed
>>>with
>>>"t_relay_to_udp(x.x.x.x, "5060");"
>>> But how can I implement a quick failover including
>>>load-distribution
>>>between those gatways?
>>> I.e. if I receive "busy here" or no response after a short period
>>>after the "invite", the call should be redirected to the other GW.
>>>
>>>Thanks in advance for your help!
>>>
>>>Best regards,
>>>Gerhard
>>>
>>>
>>
>>>_______________________________________________
>>>Serusers mailing list
>>>serusers(a)lists.iptel.org
>>>http://lists.iptel.org/mailman/listinfo/serusers
>>
>
>_______________________________________________
>Serusers mailing list
>serusers(a)lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers