State of knowledge

January 2025

estos ProCall 8 Enterprise

estos ProCall 7 Enterprise (End-of-Life EOL)

Observation

If a call is made with a softphone line (SIP subscriber individually registered or SIP trunk subscriber line), generates a second call to this line (call to "busy" ) does not generate a journal entry in the ProCall Client.

Background

In most cases, the second call is not signaled in the estos SIP gateway because it is intercepted by the telephone system.

Solution/Procedure

Activate the UCServer debug logs and (optonally) start the Wireshark trace on the UCServer host.

Adjust the behaviouraccording to.

Use the ProCall Enterprise Server logs sipav_yyyyy_mm_dd_hh_mm.txt or using the PCAP trace tocheck whether the second call was signalled to the estos UCServer SIP gateway.

A call or second call is signalled in the sipav_yyyyy_mm_dd_hh_mm.txt log files as follows, for example:

30.01.2025 07:39:14:917;32;ENetUDPConReceiverThreadFunc-6832;SIPAV;---> REQUEST FROM 10.11.12.13:5060 TO 10.11.12.14:49812
################################################################################
INVITE sip:479@10.11.12.14:49812 SIP/2.0
Accept: application/sdp
Via: SIP/2.0/UDP 10.11.12.13;branch=z9hG4bKee345a471cde09aab;rport
Max-Forwards: 70
From: <sip:00815136856177@10.11.12.13>;tag=01b5707c45
To: <sip:479@10.11.12.14:49812>
Call-ID: 53e95ea0224fcc3b
CSeq: 2091628537 INVITE
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, REFER, PRACK, UPDATE
Contact: <sip:00815136856177@10.11.12.13>
P-Asserted-Identity: <sip:00815136856177@10.11.12.13>
User-Agent: OpenScape Business M5T SIP Stack/4.2.20.35
X-Siemens-Call-Type: ST-insecure
Alert-Info: <Bellcore-dr2>;info=alert-external
Content-Type: application/sdp
Content-Length: 320

(SDP removed)
CODE


In a more extensive PCAP trace, the INVITE dialogues can be filtered in Wireshark using the display filter sip.Method==INVITE. The calls or second calls are shown here as follows:

Session Initiation Protocol (INVITE)
    Request-Line: INVITE sip:479@10.11.12.14:49812 SIP/2.0
        Method: INVITE
        Request-URI: sip:330@10.11.12.14:49812
        [Resent Packet: False]
    Message Header
        Accept: application/sdp
        Via: SIP/2.0/UDP 10.11.12.13;branch=z9hG4bKee345a471cde09aab;rport
        Max-Forwards: 70
        From: <sip:00815136856177@10.11.12.13>;tag=01b5707c45
        To: <sip:479@10.11.12.14:49812>
        Call-ID: 53e95ea0224fcc3b
        [Generated Call-ID: 53e95ea0224fcc3b]
        CSeq: 2091628537 INVITE
        Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, REFER, PRACK, UPDATE
        Contact: <sip:00815136856177@10.11.12.13>
        P-Asserted-Identity: <sip:00815136856177@10.11.12.13>
        User-Agent: OpenScape Business M5T SIP Stack/4.2.20.35
        X-Siemens-Call-Type: ST-insecure
        Alert-Info: <Bellcore-dr2>;info=alert-external
        Content-Type: application/sdp
        Content-Length: 320
    Message Body
CODE

Is the second call signaled in the SIP gateway?

NOCheck the PBX configuration.
YESContact estos product support and provide UCServer debug logs and PCAP recording.

Further information

Creating a debug log for UCServer

Create PCAP record file/trace for UCServer – network analysis

How to create a ticket for estos support