CID parsing on DirectSIP Calls?

Status
Not open for further replies.

Thomas-Pam

Customer
Joined
Dec 20, 2019
Messages
2
Reaction score
0
Hello,
new to 3cx with a bit tricky setup.
We are using a phone forwarding service for some numbers and they luckily allow to forward by a direct sip connection.
So far that also works, I got one account open to that access and calls are coming in.
Unfortunately the calls are shown with an empty CID even though the service is delivering the number.
An incoming calls looks like that:
12/16/2019 12:43:20 PM - [CM503001]: Call(C:466): Incoming call from DirSip:DirectSIP<<" " <sip:[email protected]>;tag=174XXX-17B3 to <sip:[email protected]:0>

On the clients the call seems to be coming from an empty caller, instead of using the number which is given.
The forwarding service is telling that we should parse it from the FROM header and we are not ... any way that we can configure that accordingly?
Or how could I manage to get the originating number correctly?

Thanks,

Thomas
 
Hi Thomas,

This depends on a few things. If this was a regular trunk we could adjust from which fields we read the CID

For Direct SIP we use some default fields which are not adjustable. So I would imagine that unless the forwarding service has an option to allow you to adjust what field they send the CID to you, then it may not be possible to read the CID.

However, I would recommend to run a capture on your system (from Activity Log) and make a direct SIP call. Then stop the capture, download it, and analyze it in wireshark to see which fields they send what.
 
Hi John,

thanks for the reply.
I'll surely do the capture, maybe we can figure something out - their support is quite responsive.

Could you name the default fields which you are using?


thanks,
Thomas
 
The caller ID will be read at

From: Userpart
 
Hi John,

thanks for the reply.
I'll surely do the capture, maybe we can figure something out - their support is quite responsive.

Could you name the default fields which you are using?


thanks,
Thomas

I'm guessing it will be the empty field in the capture :)
 
Status
Not open for further replies.