Ascom dect system

provit

Platinum Partner
Joined
Nov 18, 2013
Messages
3
Reaction score
2
Ascom dect sistemlerinde v20 öncesi isim bilgisi dect telefonlarına gönderiliyordu.

v20'den sonra sadece rakam bilgisi gönderiliyor.
Bunun bir çözümü var mı?
 
When posting to the forums of 3CX, please use English. We also have a Turkish forum that you can post in Turkish https://www.3cx.com.tr/forum/

Having said that, the particular system you have mentioned is not a supported by 3CX device, so we cannot objectively know its capabilities.

Is this for internal extensions? Or from external callers? A bit more information for the community would be appreciated.
 
  • Like
Reactions: N_G
In Ascom dect systems before v20, name information was sent to dect phones.

After v20, only number information is sent.
Is there a solution to this?
Only for internal calls
I know 3cx does not support it
 
  • Like
Reactions: N_G
3CX does send the name information for internal extensions. You can verify this from a wireshark capture. Then you can see what settings that DECT system has and why it is not passing it through.

You would be able to get the INVITE structure from the capture and see with the vendor why they are not parsing the information sent.
 
  • Like
Reactions: N_G
Merhaba,
Wireshark günlükleri ekteki gibidir
ascom'ların dahili aramalarında sadece isim bilgisi alınmıyor.
teşekkürler
 
We have the exact same problem with the ASCOM dect system. Call handling has changed from v18 to v20 regarding name displaying.
Is there a fix known? @provit
 
  • Like
Reactions: N_G
Hey @provit and @Lamote Matthias :
you have a fix ?
We have the same issue when dect to dect call is intitiated > no name information.
Thanks for any information about that issue.
 
Hey @hafi18 and @provit . 3cx won't help , as stated aboven due to "not supported". Somewhat understandable but we are risking losing the client over it. Also "nothing has changed from v18 to 20" is incorrect. But not many seem to know what changed. Ascom needs more/enough complaints to investigate further. Can we get in touch? Maybe we can build a case together?
 
  • Like
Reactions: N_G
Hi @Lamote Matthias ,
In my opinion, ascom can handle this very easily:
The display name or name, which is present in the SIP subscriber, would simply have to be sent in the SIP FROM display part.
But this is not the case.
If ASCOM were to fill the “display part” with data, the 3CX would also pass this on and display it clearly on the second handset.

Do you have contact with ASCOM? Unfortunately not - I would be happy to discuss this with you.
 
  • Like
Reactions: N_G
In Ascom dect systems before v20, name information was sent to dect phones.

After v20, only number information is sent.
Is there a solution to this?
Only for internal calls
I know 3cx does not support it
We have the same problem: please contact me via direct message.
 
  • Like
Reactions: N_G
We have the same problem with Ascom i62 and Ascom i63
 
  • Like
Reactions: N_G
Hello,

Can anyone make a SIP trace to 'see' the information being passed?
Only REAL details can make a difference.

Paulo
 
  • Like
Reactions: N_G
I'm attaching the call log from an Ascom to a 3CX client.
The name appears on the client during the call, while the AuthID appears in the call log (I'm attaching a screenshot).

I've performed two more tests.

If I call Ascom from Ascom, the AuthID appears on the display.

If I call Ascom from the 3CX client, the extension name appears correctly on Ascom.

This leads me to believe that Ascom devices display the AuthID in the from field instead of the extension name during calls.
 

Attachments

  • Like
Reactions: N_G
I confirm my hypothesis

1759311635231.png
 
  • Like
Reactions: N_G
Hello,

In the trace I can see the following:
560 -> 524 (From: User Field: UD0QSfVBWa -> Edoardo)
524 -> 560 (From: User Field: Edoardo -> UD0QSfVBWa)

It seems the field: "FromDisplayName" does not contain the correct information.


Can you export the Trunk configuration (goto admin, trunk and at the line of the trunk, the 3 dots, select export).
Please check what is on the line for:

<field name="ParameterIn" custom="" parameter="FromDisplayName">$CallerName</field>
...
<field name="ParameterOut" custom="" parameter="FromDisplayName">$OutboundCallerId</field>

This is how far my knowledge does go...
Hope some other people can help as well, but do please get the trunk configuration from the export.

Paulo
 
  • Like
Reactions: N_G
<field name="ParameterIn" custom="" parameter="FromDisplayName">$CallerName</field> it is not present

Screenshot 2025-10-01 alle 12.06.51.png
 
  • Like
Reactions: N_G
Screenshot 2025-10-02 alle 14.11.49.pngOr tried to modify these parameters in trunk setting without success
 

Attachments

  • 1759408699685.png
    1759408699685.png
    89.6 KB · Views: 3
  • Like
Reactions: N_G
Hello,


Just a wild guess as I do not have an Ascom installation, could you try this:

1759409133327.png

Paulo
 
  • Like
Reactions: N_G
If ASCOM are able and ready to troubleshoot this from their end we will certainly answer any interop questions they may have. But its something they must do from their end not only because its their hardware and we don't have it but also because they must verify any firmware changes they make. So please contact ASCOM and tell them to check it out and see if they can fix it and if they have questions they can ask us. You can refer to this forum post and I will inform our support...
 

Forum statistics

Threads
111,955
Messages
589,925
Members
164,853
Latest member
as7h