Bad XMLin CSTA Response ???

[Bill H]

As I dig a little deeper each day or so into CSTA, find a few more obstacles.

 

It looks like there may be some bad XML in one of the responses from SnomOne (Actually a PBXNSIP CS-410 with 4.0.1.3499 (Linux))

 

Please keep in mind that I am not an expert with XML.

 

I just know how to parse it.

 

=========================================================================================

 

<?xml version="1.0" encoding="UTF-8" ?>

 

<OriginatedEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed4">

 

<monitorCrossRefID>301206368</monitorCrossRefID>

 

<originatedConnection>

<callID>3c26845888ba-mqiegnxohpne#8b8f84f477</callID>

<deviceID>42@localhost</deviceID>

</originatedConnection>

 

<callingDevice>

<deviceIdentifier>42@localhost</deviceIdentifier>

</callingDevice>

 

<calledDevice>

<deviceIdentifier>41@localhost</deviceIdentifier>

</calledDevice>

 

<localConnectionInfo>connected</localConnectionInfo>

 

<cause>normal</cause>

 

</OriginatedEvent> ============================== Should be at the end of the XML ???

 

 

</callID>

 

<deviceID>41@localhost</deviceID>

 

</connection> =================================== Is this needed ???

 

<alertingDevice>

<deviceIdentifier>41@localhost</deviceIdentifier>

</alertingDevice>

 

<callingDevice>

<deviceIdentifier>42@localhost</deviceIdentifier>

</callingDevice>

 

<calledDevice>

<deviceIdentifier>41@localhost</deviceIdentifier>

</calledDevice>

 

<lastRedirectionDevice>

<notKnown /> =========================================== Extra White Space

</lastRedirectionDevice>

 

<localConnectionInfo>alerting</localConnectionInfo>

 

<cause>normal</cause>

 

</DeliveredEvent> ========================================== Is this needed ???

 

 

===================================================================================

 

Thanks

[mattlandis]

Bill,

 

I'm noticing the same. I'm certainly neither a csta or xml expert so i presume I'm the culprit but I'm starting to not do that. ;-)

 

The cool thing is that snom has the foresight to be working on csta. some of the other vendors are not.

[Bill H]

Matt,

 

I know what you mean.

 

I went on for a few hours checking and double checking and testing my code until I finally looked in the other direction towards the PBX.

 

I think that the big difference with Snom, concerning CSTA, is that they can control both ends of the technology from a hardware point of view.

 

The phones and the PBX (software) that is.

 

Other manufactures can easily fall into the "Interoperability" zone or don't fully appreciate the added value CSTA brings to the Telecom industry.

 

The introduction of CSTA, or any other type of computer control of the phones or PBX, is welcome here and allows a variety of exciting applications to be developed.

 

If I discover any more bugs, I will post them in this forum.

 

Bill H

[mattlandis]

While it would be nice if snom would list known issues it is very appreciated that they are forthright about what needs fixing when asked. I've worked with vendors who are not and that can extremely frustrating.

[pbx support]

=============================================================

</OriginatedEvent> ============================== Should be at the end of the XML ???

 

Looking at the code(4.2 latest), yes, that should be the end of the XML. Are you really seeing the extra data on the wire?

Not sure if 4.0.1.3499 had any issues.

[Bill H]

Looking at the code(4.2 latest), yes, that should be the end of the XML. Are you really seeing the extra data on the wire?

Not sure if 4.0.1.3499 had any issues.

 

 

Yes, the XML I placed in my original post was what I received from the CS-410.

 

I think I had a licensing problem once before when I tried to upgrade the PBXNSIP CS-410 to a newer version of SnomOne.

 

I can send you my existing License Key and maybe it can be updated as well if I have a problem???

 

Thanks,

 

Bill H