ISDN Caller-ID (1 Viewer)

[mPod]

ISDN caller-ID support is in CVS now. This means, it will be available in CVS versions and the 0.1.3.0 release version.

If you like to try it, you can get the latest CVS version here: http://www.myshare.de

To use the plugin, enable it in the plugin's section of configuration.exe. No additional setup available at the moment.



Area- & country-codes

For now, the XML file contains area-codes for Austria, Croatia, Germany and Luxembourg only. Be my guest and add your countries to the list.
Add your area-codes to the existing file "ISDNCodes.xml" in the Media Portal root directory.
After you edited it, send it in, please, to include it in the official distribution.



Configuring windows TAPI settings

Make sure that you have configured your dialing location properly. Otherwise the number cannot be recognized. Don't forget your country!
You can configure it in your control panel (Systemsteuerung).

It doesn't matter if you enter your area code with or without the leading zero.
Example: For Berlin, Germany you can enter 030 or 30. Both versions work with the plugin. See these pictures:

Using Outlook contacts for number lookup

The number lookup only works, if the telephone numbers are stored in canonical (international) format.

See this example for a fictitious number in Berlin, Germany:

If there are pictures embedded in your contacts, MP displays them along the other information in the popup-window.

 

[MichaelK]

Hi mPod

thanks for your great work.

you say It doesn't matter if you enter your area code with or without the leading zero. Example: For Berlin, Germany you can enter 030 or 30. Both versions work with the plugin.

When i set my areacode in the telephony options with the leading zero, then i see "ISDN: Home location: unknown (02131), Germany (+49)" in MediaPortal.log.
Without the leading zero it says "ISDN: Home location: Neuss (2131), Germany (+49)"

when i make an testcall, the window pop up and i cann see the number and an error message: "an error occured, see the logfile for details"

the logfile:

11.06.2005 19:41:24 ISDN: Home location: Neuss (2131), Germany (+49)
11.06.2005 19:41:25 ISDN: Application registered with CAPI (1)
11.06.2005 19:41:25 ISDN: CAPI signaling activated
11.06.2005 19:41:34 ISDN: CalledID: 22
11.06.2005 19:41:34 ISDN: CallerID: +0021311234567
11.06.2005 19:41:34 ISDN: Incoming call (unknown, unknown / + () 0021311234567)
11.06.2005 19:41:34 window:MediaPortal.Dialogs.GUIDialogNotify init
11.06.2005 19:41:49 key:13 0xD (2)
11.06.2005 19:41:49 Mediaportal.OnExit()
11.06.2005 19:41:49 Card:1 stop
11.06.2005 19:41:49 PlugInManager.Stop()
11.06.2005 19:41:49 Mediaportal.OnExit()
11.06.2005 19:41:49 MediaPortal done
11.06.2005 19:41:50 ISDN: CAPI released (1)

my pbx adds a leading zero for my callerslist at the phones.
i added a contact in outlook for my number, but the name
isn't displayed. i think this happens because of the leading zero
that is to much. i can try to disable the leading zero in my pbx.

sorry for posting this in this thread. i don't know if me make an
bug thread for this plugin or where i should post it.

Michael

 

[mPod]

you say It doesn't matter if you enter your area code with or without the leading zero. Example: For Berlin, Germany you can enter 030 or 30. Both versions work with the plugin.

Try a later CVS version, please. I put that in yesterday, so maybe you got a slightly too old version.

my pbx adds a leading zero for my callerslist at the phones.
i added a contact in outlook for my number, but the name
isn't displayed. i think this happens because of the leading zero
that is to much. i can try to disable the leading zero in my pbx.

Usually, when a number comes in via DSS-1 (Euro-ISDN), there is no leading zero at all. Your number should come in like: "2131797883" with the national bit set.
Putting the numbers to Outlook in your format can't work, because the plugin fails while parsing the 3 components of an incoming call. So it can't build a proper string for Outlook. The only thing which helps you is an option in the plugin. I'll put it in, I think you can test it with a CVS version tomorrow.

This place is perfect for feedback.

 

[MichaelK]

that sounds nice mpod. that is what i need. an option to delete the first "0".
in outlook i added the number like this: "+49 (2131) 1234567" , i think
that's right ?

 

[mPod]

that sounds nice mpod. that is what i need. an option to delete the first "0".
in outlook i added the number like this: "+49 (2131) 1234567" , i think
that's right ?

That's correct, yes. You can also see this in the above image.

I just committed an addition to the plugin. It's got a setup now, where you can enter the amount of digits to be removed from the beginning of a caller-ID. This should fix your problem. Of course, it needs some time to be in anonymous CVS.

 

[MichaelK]

Hi mPod

Great, i tried the cvs from this night and the deleting of the leading digits works. but the error in the popup window still exists. (an error occured, see log for details) And it recognized not the number from the outlook contact. I think this is because of the "+" sign at the beginning. Here is the log.

12.06.2005 10:04:28 ISDN: CallerID: +21311234567
12.06.2005 10:04:28 ISDN: Incoming call (Neuss, unknown / + (2131) 1234567)

the country code is normally not submitted, only if a call from another country is incoming. but the "+" is still in the string, so i think thats the reason why the number is not found in the outlook db ?

 

[mPod]

Your country code is missing for some reason. Are you sure, your dialing parameters are entered correctly in windows?

Instead of "+ (2131) 1234567" the lookup number should be "+49 (2131) 1234567". Please check your windows dialing settings.

Or do you use a too old version of "ISDNCountryCodes.xml"? The current version has a size of 11.625 Bytes.

If all this doesn't work, please post all log-lines starting with "ISDN:".

Michael, I'd also like to know if all this also happens, if you connect your ISDN adapter directly with the NTBA. Not sure if you could try that. I'm not very sure, if you get standard-ISDN commands to your card, because you're using your PBX, as you said... In case your ISDN card does not get the normal DSS1 commands, we need to do some debugging on your HTPC. It could be that the "national/international" flag is not transmitted in your configuration. Can you say for sure that your PBX is doing pure Euro-DSS1 with your ISDN card? (despite of the 0 it adds to the beginning of a number)

But first of all, make sure, your ISDNCountryCodes.xml is identical to this one (format has been changed yesterday evening): http://cvs.sourceforge.net/viewcvs....xbmc/bin/Release/ISDNCountryCodes.xml?rev=1.3

 

[MichaelK]

12.06.2005 13:48:59 ISDN: Home location: Neuss (2131), Germany (+49)
12.06.2005 13:48:59 ISDN: Application registered with CAPI (1)
12.06.2005 13:48:59 ISDN: CAPI signaling activated
12.06.2005 13:49:08 ISDN: 2
12.06.2005 13:49:08 ISDN: CalledID: 22
12.06.2005 13:49:08 ISDN: CallerID: +21311234567
12.06.2005 13:49:09 ISDN: Incoming call (Neuss, unknown / + (2131) 1234567)

thats the complete log. the area code is recognized by the plugin but not the number. it is not very easy for me to connect the isdn card directly to the ntba. when nothing else works, i will try it. but normally i would like to have the card at the internal s0 bus from my euracom pbx, because of recognizing internal calls. but i think it is normal that the country code in the own country isn't displayed ?

 

[mPod]

but i think it is normal that the country code in the own country isn't displayed ?

That's correct. But there also comes a flag with the incoming call which indicates, wheter it's an international or a national number. If the flag is national, the plugin adds your country to the number. If it's international, it puts a "+" in front of it. The number send to the ISDN card is not the number like you can see it on your phone. It's formatted a bit differently.
It looks to me that your PBX always sends this information as "international". I'll put a log entry in, that shows, what your PBX sends to the card. So we can find out, whats non-standard with your PBX and how we can work around it. Will be in the next CVS version.

 

[mPod]

I added some more logging to the code now. In your log, there will be a line similar to this one:

12.06.2005 14:50:55 ISDN: Buffer: (9)(193)12003004(12)(33)(129)3012003002

Post your ISDN log including the new line here again, so we can see, how your PBX talks to the ISDN card.