[ASTPPCOM-1356] Outbound Caller-ID from SIP device is being ignored Created: 23/Feb/23  Updated: 10/Jul/23

Status: Open
Project: ASTPP Community
Component/s: None
Affects Version/s: v6.0
Fix Version/s: v6.0

Type: Bug Priority: High
Reporter: Ramiro Davila Assignee: Alpesh Kaklottar
Resolution: Unresolved Votes: 0
Labels: new_bug
Remaining Estimate: 0h
Time Spent: 3h 35m
Original Estimate: Not Specified
Environment:

Debian 10

ASTPP6

Attachments: File caller_id_grandstream.pcap     File CLI_overwrite.mp4     PNG File image-2023-03-06-12-42-17-986.png     PNG File MicrosoftTeams-image (1).png    
Reproducibility: always
Category: Call
Edition: Community

 Description   

Good night.
Here, ASTPP 6.
Grandstream Endpoint, correctly configured, registering fine; DID assigned to endpoint, incoming calls working OK.
SIP device configuration in ASTPP looks fine, and has a "Caller Number" assigned(eg.: 5554443333)

But, when I make a call from the endpoint, ASTPP is using the Caller-ID from the endpoint, ignoring the assigned "Caller Number" 5554443333 ...

Already double-checked the following parameters:

  • Caller-Id-In-From (in Gateway config...tested true and false, same issue)
  • Extension-In-Contact (in Gateway config...tested true and false, same issue

In order to confirm the situation, I made changes in the Endpoint(programming in the phone, the Caller-ID my carrier needs to see), and this "trick" works...but I don´t think this is the correct way to solve the issue.

...I don´t know why this happens in version 6...I have working other server(version 5), and the parameters related with Caller-ID are working fine; the endpoint has his own username/CID number, and no matter this, ASTPP5 overwrites and assigns my correct CID programmed in the "SIP device" section... why this issue happens in version 6??..
...or maybe am I doing something wrong?

PS: I have tested in two separated servers both with ASTPP6, one with centOS, the second with Debian...same issue...

 Comments   
Comment by Yash Shah [ 01/Mar/23 ]

This issue is not reproduce. CID number correctly using as per configured in SIP device when i make a call from Grandstream endpoint.

Comment by Ramiro Davila [ 04/Mar/23 ]

Dear Yash Shah,

there is a missunderstanding here.

If you tell "CID number correctly using as per configured in SIP device", then what is the usage of the field named "Caller Number"..??

"Caller Number" is located in the SIP device configuration; when you create a SIP device in ASTPP, you can assign Username, Password, Voicemail Optinos, etc...and CALLER NUMBER.... right..?

In past version(ASTPP 5), this field MODIFIES ther CID coming from the SIP endpoint....no matter what CID is sent from the endpoint, ASTPP 5 modifies it and assigns the CID as desired by the Reseller or the ASTPP Admin...this is a very useful option..!

 

My reported issue reffers ASTPP version 6; this option has become UNUSABLE(does nothing); no matter what you assign in the field "Caller Number" in ASTPP6, the CID sent from the endpoint remains, bypasses ASTPP6 and (in my case) causes problems with arrives the final Carrier, who is expecting other CID format.

 

Please test the following:

  • You have a VoIP Carrier who accepts outbound calls ONLY when originated from some CID recognized or sold by them:
  • You have your Endpoint(Grandstream or other) configured as a freePBX extension Number(234 for example).
  • Extension 234 could originate local calls(using 234 internal CID) AND could originate some international calls using the VoIP Carrier, which is in the border of the network...
  • What happens if the final Carrier receives CID "234" ...? The Carrier hangs the call, because it is NOT originated from some recognized CID
  • This was the valuable reason to use the "Caller Number" field in the SIP Device configuration....you could change "234" CID and replace it by something like "1+305+9998888"

I hope been self-explained the issue.

If you cannot reproduce the situation, please trust me a little bit, or please let´s find the way of work together(some remote console or similar) in order to help you to see the case.

Sadly, I must acomplish dead-lines for deploying my projects.

If ASTPP don´t fullfills expectations, sadly (again) I should abandon this job.

 

Comment by Alpesh Kaklottar [ 06/Mar/23 ]

Hello Ramiro Davila

I go-through your use case : 

I did below set-up for CID number

[Endpoint grand-stream]-> CID number set in grands-stream is "9909999099"

[ASTPP configuration] -> CID number set in SIP device  is caller name="Alpesh" and caller number="918320997494"

Below is the sequence of call
1) Call from end-point(grand-stream) to ASTPP server -> caller ID received "9909999099"

2) ASTPP replace CID number from "9909999099" to "918320997494"

3) call from ASTPP to carrier -> Final CID number will set "918320997494"

Please go-though attachment section 

 

For your reference, i am attaching my configuration for Grand-stream, SIP devices, pcap and recorded video. 

Comment by Alpesh Kaklottar [ 06/Mar/23 ]

Please let me know if we didn't understood your exact use case yet.

Generated at Sat Feb 10 07:25:24 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.