Outgoing CID – Not Displayed - VitalPBX Community

This topic has 8 replies, 3 voices, and was last updated 6 months, 2 weeks ago by panna.

Post

- May 22, 2019 at 12:20 pm
- Quote
Ryado
Participant

Up
1
Down

Hello All,

I am currently testing outbound calls with the Vital PBX through one of our VoIP provider. I am able to successfully make an outbound call from a PBX extension to a network subscriber, however the CID of the extension is showing up as Unknown.

“Overwrite CID” is disabled. “Get CID From” is set to Default but also tried the “Contact” and “From” options.

I have asked the provider for assistance and they are expecting the “P-Asserted-Identity” field in the Invite. It is not being sent currently.

In addition, they would like “user=phone” in the Request-URI and Header

I would appreciate you guidance in helping me set/enable those two fields.

0

Viewing 8 replies - 1 through 8 (of 8 total)

Replies

- May 22, 2019 at 5:31 pm
- Quote
Jose Miguel Rivera
Keymaster
Up
0
Down

You may try the following:

Go to the devices profiles (Settings >> Technology Settings >> Profiles), select your SIP profile (By default is “Default SIP Profile”), and check the value of the field “Send Remote Party ID“, must be set to “Use PAI“.

In your trunk configurations, go to the Advanced tab, and set on custom headers section the following info:

Header: P-Asserted-Identity

Value: <sip:{CIDNUM}@{HOST}>

Enabled: Yes

In your trunk, you may set the parameter “usereqphone=yes“, in order to send “;user=phone” on URI

0
- May 27, 2019 at 11:33 am
- Quote
Ryado
Participant
Up
0
Down

Thank you for your detailed responses. I have managed to update the Default SIP Profile as requested.

For the Trunk Configurations:

Would you be able to check over the settings I have placed for PAI

In Advanced > Custom Settings

Type : Friend

Parameter: P-Asserted-Identity

Value: sip:{CIDNUM}@{HOST}

I am unable to find the parameter “usereqphone=yes” to set to yes.

The following is the versions I am running:

VitalPBX 2.1.1-1

Asterisk 13.23.1-1

Can you confirm if the parameter is available for that version. If not, is there a workaround in the meantime? However, I am getting the “;user=phone” on URI now as I have manually updated the sip__50-1-trunks.conf file.

Currently we are still unable to get the PAI. I suspect something is lacking in my configuration from the above.

0
- May 27, 2019 at 4:26 pm
- Quote
Jose Miguel Rivera
Keymaster

Up
0
Down

Sorry dude, you must update to the latest version of VitalPBX in order to send custom headers.

0
- May 27, 2019 at 4:40 pm
- Quote
Ryado
Participant

Up
0
Down

Thank you very much for the feedback. I will make the update and inform you on the outcome.

I really appreciate your assistance.

0
- May 27, 2019 at 4:41 pm
- Quote
Jose Miguel Rivera
Keymaster

Up
0
Down

You’re welcome

0
- May 28, 2019 at 4:01 pm
- Quote
Ryado
Participant
Up
0
Down

Hello again,

Is there a simple way to rollback to the current software version in the event of any issues with the new version?

In addition, can yo confirm the following is the update procedure:

Clean cache: yum clean all

Update to Latest version: yum update vitalpbx

0
- May 28, 2019 at 4:05 pm
- Quote
Jose Miguel Rivera
Keymaster

Up
0
Down

No, until now is not possible to do a rollback.

About the procedure of updating VitalPBX, the answer is yes, that’s the procedure.

0
- March 4, 2021 at 5:18 am
- Quote
panna
Participant

Up
0
Down

Hi,
I am also unable to find the place to set the parameter “usereqphone=yes”.

I am running the following version:

Carrier Plus 3.0.6-2
Asterisk 18.1.1-1
DAHDI 2.11.1-7

0