QSIG data contains

[rnbarrett]

We are trying to interface our F9600 (R15) with Cisco's CUCM. DMS-100 trunks won't work for us, so we are testing using QSIG. However, the QSIG data from the Fujitsu is not in a format that the Cisco gateway understands, and vice-versa. This is a behvaior controlled by the SVP,2,243 setting for QSIG name display. Cisco has explained the problem to us in the wording below. Does anyone know if/how to configure the Fujitsu to specify the operation identifier as either a global or local value, not both? Also - there is no Cisco setting that will help in this situation. We've tried them all, and we've tried with CUCM 8.6 and CUCM 9.1.

"The Fujitsu PBX does not properly encode the Calling Name information in the Q.Sig FACILITY Information Element. According to the ECMA 164 and ECMA 165 specifications, the operation identifier should be specified as either the local value or global value. From our analysis of the messages coming from the Fujitsu, it appears that it is sending both the local as well as global value which is against the specification."

 

[NewNic]

Back in the day, Fujitsu would only support ANI over Qsig. Name would get passed but as you are finding out the other end can not decipher.

The qsig spec for the Fujitsu is ECMA E164 3rd addition
You can integrate fully to an Avaya, But with cisco your outa luck

 

[rnbarrett]

That's just it - the behavior we are currently seeing is not ECMA 164 3rd Edition or 2nd Edition compliant.

For us, it no longer matters. We worked around it. We have a SIP Normalization script fixing the calling name for Fujitsu --> Cisco calls over a QSIG trunk, while all Cisco --> Fujitsu calls go over a DMS-100 trunk where everything works (calling name, called name, connected name, etc.). No Avaya gateway necessary if you can live without called name and connected name.

If you can use DMS-100 for everything, life is good between Fujitsu and Cisco. However, we have some specific configuration on the Fujitsu that requires us to use QSIG in order to properly migrate numbers to the Cisco. Go figure.