Hello,
It’s the continuation of the trouble about QSIG call transfer is being presented with the internal extension number of the transferred calls and never show the external ANI.
Yesterday I upgraded the IPO to the 1.4.25 and test again but I not found any relevant diference about my trouble, when a external call received on the HiCom was transfer
Trought the E1 Qsig to the IPO, the IPO only show at the display and the phone manager the number of the phone who made the transfer and never the external PSTN ANI.
We test with a lot of protocols variants on the HiCom Qsig , but in all cases I saw the same behaviour.
Thank for the answers, MrIpo but I have some questions:
Special I’m not fully understand your phrase:
“It ended up being the programming on the connecting pabx and require a software upgrade. The connecting PABX had to be programmed to pass the DDI through to the IPO as part of its call setup on the IPO in QSIG A configuration”
What’s mean that the connecting PABX (in your case a Ericsson MD110) pass the DDI to the IPO as part of the call setup and in which part ?
1) The software upgrade was in the MD110 or in the IPO ?
2) In your scenario, finally the IPO show the correct external (Public PSTN) ANI for a call transfer from the MD110 at the display and the phone manager ?
Yesterday I made the test with the company that sold the HiCom , the HiCom has a lot of variants about Qsig (ECMA v1 seg 1, ECMA v1 seg 9, ECMA v2 seg 1, PSS1, EDSS1Net, etc, etc ), An the IPO has only Qsig-A and Qsig-B.
Some combination of protocols version works only in one way for a simple call setup.
Only some combination works for two way call setup:
IPO (v1.3.34) with Q-sig B and HiCom with ECMA v1 seg 1 or EDSS1Net.
What is the difference between Qsig A and B ?
I saw that with Qsig-A at the IPO side the link never goes up.
In all cases HiCom send the external ANI as a facility Q.931 message after the call is transferred.
Siemens people say that it is not possible to change this behaviour.
In the case of the MD110, in which part of the message setup it send the ANI , Could you
Provide me a IPO trace ?
A lot of Thanks.
Gustavo.
Answer from MrIpo:
My first suggestion would be to upgrade to 1.4(22) or 1.4(25) when its released.
With 1.4(X) the IPO comforms to
Supplementary Service ETSI Reference
Simple Telephony Call/Basic Call ETS300 171/172
Circuit Switched Data Call/Basic Call ETS300 171/172
Called/Calling Line ID Presentation ETS300 173
Called/Calling Name Presentation ETS300 237/238
Message Waiting EN301 260/
We have done the configuration you are speaking of many times. In your case here The IPO on its QSIG call setup is being presented with the internal extension number of the connecting PABX as you have noted. We had this same case when connecting a IPO to Eccrission MD110 via E1. It ended up being the programming on the connecting pabx and require a software upgrade. The connecting PABX had to be programmed to pass the DDI through to the IPO as part of its call setup on the IPO in QSIG A configuration.
You have also probley seen that when you connect QSIG A-B configuration via PRO card on the IP, the incoming call bypasses Incoming call routs and looks directly at extension number with a match or direct to System Short code and into VM Pro for AA configuration.
Hope this helps
