Ron hotmail ha scritto:
The short answer is no, you will never have a situation where the
'local' part of the term number is mistaken for part of the dialcode.
for example,
your customer dials 0119647701773352 (Iraq mobile number)
Iraq011964
Iraq-Baghdad 0119641
On Fri, January 27, 2006 23:47, Script Head said:
What you're trying to accomplish can be easily done with an SQL query. You
need to create a table of all the prefixes (international dial+country
code+city/carrier) and join by that prefix.
On 1/27/06, Damon Estep [EMAIL PROTECTED] wrote:
There is second single digit code - 7 (Russia).
On Sat, 2006-01-28 at 18:41 +0100, Francesco Peeters (Asterisk) wrote:
Only one country has a single digit code: USA = 1
___
--Bandwidth and Colocation provided by Easynews.com --
Can anyone shed some light on rules that might make the task of
parsing the country code and city codes from a dialed number in the
CDRs?
I know that there is almost never a case where a concatenated country
and city code could overlap with another country code, but what about
city codes and
What you're trying to accomplish can be easily done with an SQL query. You need to create a table of all the prefixes (international dial+country code+city/carrier) and join by that prefix.
On 1/27/06, Damon Estep [EMAIL PROTECTED] wrote:
Can anyone shed some light on rules that might make the
be mistaken for another
country code.
D
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Script Head
Sent: Friday, January 27, 2006
3:47 PM
To: Asterisk
Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] OT?:
International number parsing
PM
Subject: RE: [Asterisk-Users] OT?:
International number parsing
Agreed, that is what
I plan to do, but do you know if the numbering plans are such that a
countrycode+citycode+”portion of a local number” could ever be mistaken for a
different country/city combination
Sent: Friday, January 27, 2006
8:17 PM
To: Asterisk
Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] OT?:
International number parsing
It realy is a pain in the *ss.
the problem is just how you explained. when trying to
match the terminating number, there's
: RE: [Asterisk-Users] OT?:
International number parsing
Have you seen
situations where a portion of the local number, when added to the country and
city code, result in a longer match then the actual country/city called and
therefore an inaccurate match?
From
