Telephone numbering plan (e.164 infos)
Ralf Jänike
Alcatel, Siemens, Estos ... TAPI 2.x) and distributes information about
current Calls to connected Client-Components.
Now i got in trouble with the telephone numbers i get from the TSP. There
are no leading 0 (Zeroes) for national and international calls, so the
number you are seeing on the screen isn't the number you're seeing on the
telephone or the number you have to type in your telephone to call the
other party.
Questions:
-Are there information about the call origin in the TAPI stream (CALLINFO
Structure)?
-Especially the e.164 flags that tell me if it is a national or
international call so i can prepend 0 or 00 my self?
-Is there a tapi call to translate a number to canonical format? (i know
there is linetranslate, but it works the opposite way)
Matthias Moetje [MVP]
> -Are there information about the call origin in the TAPI stream (CALLINFO
> Structure)?
There is some call origin information but it only indicates if it is
internal to
the PBX or external.
> -Especially the e.164 flags that tell me if it is a national or
> international call so i can prepend 0 or 00 my self?
AFAIK, there isn't, but most PBXs give you a a consistent
caller ID so that you always prefix the same digits to all
(external) numbers.
> -Is there a tapi call to translate a number to canonical format? (i know
> there is linetranslate, but it works the opposite way)
No, because even in theory this is not possible. To convert to canonical
an application would need to know all existing area codes in all
countries...
Otherwise you can't know the length of the area code and are this unable
to create the canonical format.
Best regards,
Matthias Moetje
-------------------------------------
TAPI WIKI: http://www.tapi.info
-------------------------------------
TERASENS GmbH
Augustenstraße 24
80333 Munich, GERMANY
-------------------------------------
e-mail: moetje at terasens dot com
www: www.terasens.com
-------------------------------------
Ralf Jänike
> caller ID so that you always prefix the same digits to all
> (external) numbers.
Yeah, they give me consistent caller id without any leading 0, so i don't
know if i have to prepend only 1 or even 2 0 (zero) to indicate to the
user the call is coming from another country or not. In ISDN there are
flags that indicate national or international (or subscriber or ...) so
you can prepend the missing numbers. the biggest problem is, the caller id
is displayed on the telephones with all leading 0 so user can use the
displayed number to call back.
ciao Ralf
On Thu, 30 Oct 2008 01:39:18 +0100, Matthias Moetje [MVP]
<moetje@terasens_nospam_.de> wrote:
> Ralf,
>
>> -Are there information about the call origin in the TAPI stream
>> (CALLINFO
>> Structure)?
> There is some call origin information but it only indicates if it is
> internal to
> the PBX or external.
yeah, i know, but this post is only about external calls
>
>> -Especially the e.164 flags that tell me if it is a national or
>> international call so i can prepend 0 or 00 my self?
>
> AFAIK, there isn't, but most PBXs give you a a consistent
> caller ID so that you always prefix the same digits to all
> (external) numbers.
>
>> -Is there a tapi call to translate a number to canonical format? (i know
>> there is linetranslate, but it works the opposite way)
>
> No, because even in theory this is not possible. To convert to canonical
> an application would need to know all existing area codes in all
> countries...
> Otherwise you can't know the length of the area code and are this unable
> to create the canonical format.
>
> Best regards,
>
> Matthias Moetje
> -------------------------------------
> TAPI WIKI: http://www.tapi.info
> -------------------------------------
> TERASENS GmbH
> Augustenstraße 24
> 80333 Munich, GERMANY
> -------------------------------------
> e-mail: moetje at terasens dot com
> www: www.terasens.com
> -------------------------------------
>
>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Matthias Moetje [MVP]
> Yeah, they give me consistent caller id without any leading 0, so i don't
> know if i have to prepend only 1 or even 2 0 (zero) to indicate to the
> user the call is coming from another country or not.
I remember having this same problem with a HiPath PBX some time ago
(i.e. not a single 0 prefix), but it was just a configuration issue. In fact
I was able to configure it to report the correct number of 0's in all
cases. Unfortunately I don't remember which setting it was...
![Andreas Marschall [MVP TAPI]'s profile photo](http://lh3.googleusercontent.com/a-/ALV-UjUdVhINZ75uvCzmDvRIjAQ_KkFrrjQd-XqxpwhoppRsppj2w5gW=s40-c)
Andreas Marschall [MVP TAPI]
news:op.ujugd...@dreielch.hq.ferrari-electronic.de...
> Yeah, they give me consistent caller id without any leading 0, so i don't
> know if i have to prepend only 1 or even 2 0 (zero) to indicate to the
> user the call is coming from another country or not. In ISDN there are
> flags that indicate national or international (or subscriber or ...) so
> you can prepend the missing numbers. the biggest problem is, the caller id
> is displayed on the telephones with all leading 0 so user can use the
> displayed number to call back.
Ralf,
what PBX / TSP are you using?
--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK / Visual C++
TAPI / TSP Developer and Tester
My TAPI and TSPI FAQ:
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
My TotoŽ Tools (a collection of free, mostly TAPI related tools):
http://www.i-b-a-m.de/Andreas_Marschall's_Toto_Tools.htm
TAPI development around the world (Frappr! map):
http://www.frappr.com/TAPIaroundTheWorld
* Please post all messages and replies to the newsgroup so all may
* benefit from the discussion. Private mail is usually not replied to.
* This posting is provided "AS IS" with no warranties, and confers no rights.
Andreas Marschall [MVP TAPI]
news:O1U0hutO...@TK2MSFTNGP04.phx.gbl...
> I remember having this same problem with a HiPath PBX some time ago
> (i.e. not a single 0 prefix), but it was just a configuration issue. In fact
> I was able to configure it to report the correct number of 0's in all
> cases. Unfortunately I don't remember which setting it was...
Matthias,
in HiPath 3000 Manager E it is under menu
Settings / System parameters / Plus Product Flags:
There you need to mark the checkbox "Direction prefix send via CSTA".
--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK / Visual C++
TAPI / TSP Developer and Tester
My TAPI and TSPI FAQ:
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
My Toto® Tools (a collection of free, mostly TAPI related tools):
Ralf Jänike
other cases it were alcatel OXE and OXO with Alcatel 4400 TSP or Estos
ECSTA
other cases it where Siemens PBXs (or Octopus) with Estos ECSTA or Siemens
120/170 TSP
i think the problem can only be solved on the PBX or CSTA side of
telephony but not in a TAPI application. i may just prepend 1 0 dependent
on caller id length but it wouldn't be a reliable solution for
international calls. i think i have to write me some papers where to find
the configuration settings in PBXs.
thanks Ralf
On Fri, 31 Oct 2008 20:16:23 +0100, Andreas Marschall [MVP TAPI]
<Andreas....@i-b-a-m.de> wrote:
> "Ralf Jänike" <meine_mai...@nurfuerspam.de> schrieb im Newsbeitrag
> news:op.ujugd...@dreielch.hq.ferrari-electronic.de...
>> Yeah, they give me consistent caller id without any leading 0, so i
>> don't
>> know if i have to prepend only 1 or even 2 0 (zero) to indicate to the
>> user the call is coming from another country or not. In ISDN there are
>> flags that indicate national or international (or subscriber or ...) so
>> you can prepend the missing numbers. the biggest problem is, the caller
>> id
>> is displayed on the telephones with all leading 0 so user can use the
>> displayed number to call back.
>
> Ralf,
> what PBX / TSP are you using?
>
--
Ralf Jänike
noted and printed it
Ralf
On Fri, 31 Oct 2008 20:24:14 +0100, Andreas Marschall [MVP TAPI]
<Andreas....@i-b-a-m.de> wrote:
> "Matthias Moetje [MVP]" <moetje@terasens_nospam_.de> schrieb im
> Newsbeitrag
> news:O1U0hutO...@TK2MSFTNGP04.phx.gbl...
>> I remember having this same problem with a HiPath PBX some time ago
>> (i.e. not a single 0 prefix), but it was just a configuration issue. In
>> fact
>> I was able to configure it to report the correct number of 0's in all
>> cases. Unfortunately I don't remember which setting it was...
>
> Matthias,
> in HiPath 3000 Manager E it is under menu
> Settings / System parameters / Plus Product Flags:
> There you need to mark the checkbox "Direction prefix send via CSTA".
>
--
Andreas Marschall [MVP TAPI]
news:op.uj1ap...@dreielch.hq.ferrari-electronic.de...
> last case it was cisco callamanger 4.2 with cisco tsp
> other cases it were alcatel OXE and OXO with Alcatel 4400 TSP or Estos
> ECSTA
> other cases it where Siemens PBXs (or Octopus) with Estos ECSTA or Siemens
> 120/170 TSP
Ralf,
ok, so this seems a common issue for multiple PBXs / TSPs.
For HiPath 3000 familiy I posted how to reconfigure this in another reply
within this thread.
> i think the problem can only be solved on the PBX or CSTA side of
> telephony but not in a TAPI application.
Yes, I think so.
> i may just prepend 1 0 dependent
> on caller id length but it wouldn't be a reliable solution for
> international calls.
Yes, due to the variable length of callnumbers.
> i think i have to write me some papers where to find
> the configuration settings in PBXs.
Feel free to share this with us...
--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK / Visual C++
TAPI / TSP Developer and Tester
My TAPI and TSPI FAQ:
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
My Toto� Tools (a collection of free, mostly TAPI related tools):
Andreas Marschall [MVP TAPI]
> > in HiPath 3000 Manager E it is under menu
> > Settings / System parameters / Plus Product Flags:
> > There you need to mark the checkbox "Direction prefix send via CSTA".
> thanks,
> noted and printed it
Ralf, you are welcome.