Thanks, Stephan

You mean I should call JTAPI/TAPI directly change CCM 5.0 DB filed , right ?

I find two DB fileds like below from <>

2.3.117.41 fkcallingsearchspace_mwi (FI-1078)

2.3.119 numplandynamic (TI-334)

But I can't find how to implement it . Could you give me some references about that or some

examples ? I am sorry for my fool.

Best Regards

I never checked what happens on a database level. However, for any actions that have a direct influence on a device, writing directly into the database is the wrong approach.

As an example: if you set a forward (callforward all) via database (and not AXL), calls may well be forwarded, but the phone's status won't be adapted (so you don't have the callforward indicator and no information about the callforward). If you set the callforward via JTAPI or AXL, the phone's status will also be updated to show that it has been forwarded.

When you configure a phone, you'll see the same thing in many cases.. especially in older CCM releases, you were often told that you need to reset the phone to apply a change you've made. In newer versions, this is often (but not always done automatically.. you'll see the phone restart after pressing update).. it's the same thing here.. you write into the database, but then you also have to apply those changes to the phone (one good example is changing a line label.. you won't get the label to change on the phone by just writing to the database.. you have to restart the phone for it to load the new label name).

Even if you need to get the mwi status, JTAPI will do that for you (CiscoAddress.getMessageWaiting - and to set it, it's CiscoAddress.setMessageWaiting). Since you need a CTI command to set the MWI, you can as well resort to CTI to get the MWI status as well and don't bother with the database.

fkcallingsearchspace_mwi is definitely not it though - I can tell you that without looking at the diagram since fk_anything is a foreign key and you have an uuid value in that field. The mwi status would be a boolean since it can have just two values. In fact, it's numplan.ismessagewaitingon but as I said.. with any element that has a direct influence on a phone's appearance or behavior, you cannot just change it... at best you need a phone reset. And if you do it with JTAPI (and probably TAPI too.. I can't be sure because I've never done TAPI and hope to never have to), you can change the MWI status on the fly without having to restart the phone, which is much more elegant.

Hi,

Another simple way to put the MWI ON / OFF is to push a ciscoiphoneexecute Dial to the ipphone with the number of the MWI ON / OFF

Hi,rcronier

Thanks for your reply. I am newer for Unified Communications. Could you mean use AXL ? Then

make a call to the ipphone and dial with the number of the MWI ON /OFF ?

Best Regards

Hi,

It is not AXL.

IPP have a web server that can interpret commands.

You can send XML to IPP (via their IP) and tell them to execute some command like dialing, press button etc ...

For your question :

MWI ON & Off are just number on CUCC

so if on a phone you dial the MWI ON Number, the phone will automatically light the lamp.

and so on if you dial MWI off

You can try this easilly if you have a IPP.

So the idea I suggest is to push XML command to the phone to execute a Dial to MWI ON or OFF

It is very simple, the difficulty is to find all IP Adress of you IPP that you want to control

Example of request to send To IPP :

Hi,rcronier

Thanks for your reply!

Push XML command to the phone to execute a Dial to MWI ON /OFF , it is direct and simple method.

I try press extension MWI ON number on IPP, the lamp light, and really simple. :)

But do like that , the application who send xml will not communicate with CCM ,right ?

If I use JTAPI/TAPI , initialize a line , and make a call to phonenumber with MWI ON , it will implement same function , is it ?

Best Regards

hi Richard

Indeed, if you initiate a call in Tapi/Jtapi it will do the same.

My opinion is that it is just a little more complicate to initiate a call with JTAPI/TAPI, create a provider/superprovider, create observerse, what else .. than send an XML POST to a phone.

But it is your choice ;-)

Good Luck, don't hesitate

R?my

Hi,rcronier

Thank you very much. I know more from you.

Best Regards

Hi,Stephan

Thanks for your patience and care!

I look for <>, find Cisco TAPI doesn't support PhoneGetLamp and PhoneSetLamp.

I will follow your direction (CiscoAddress.getMessageWaiting - and to set it, it's CiscoAddress.setMessageWaiting), learn about that.

Thanks again !

Best Regards

Hi,Axel

Could you supply your implement of thought? I mean how do you implement MWI with TAPI step by step.

initialize a line -> select a phone, go on ???

Best Regards

... dial ?!

We are not using TAPI, we are using SIP and it works like a charm!

Regards

Axel

Do you means directly send SIP message to IP Phone?

I am a newbie. Could you guide me more clearly?

Best Regards

Richard