V20 Emergency calling CID override

[SpeedyPH]

On V18, I am able to set the outbound CID for emergency calls to a different number. V20 will only call out on the main number listed in the SIP Trunk.

On V18, I will have the main number on the SIP trunk and have all the other numbers listed in the DID tab. I don't put CID on the outbound rule. I put the CID information in each user extension. Then when I specify a CID on the emergency numbers page, this CID will override anything else. This is not working with V20. I have tried setting CID on the extensions and the outbound rule and can't get any number to work other than the number listed on the SIP Trunk as the main number. All settings on the SIP provider side are the same between V18 and V20 systems.

The reason I need to be able to do this is because I set up a new PBX for a customer. I set them up with a temporary number from my service provider. I then set up the PBX with all their information and their numbers and then add the temporary number in as an additional DID. I then forward their existing phone lines to the temporary number while I start the porting process. Their numbers are registered with my sip provider so that I can call out using their phone number during the porting process but I can't activate E911 on their number until the porting completes. So, I need to be able to force CID to be the temporary number when dialing 911 so that it's registered with E911.

Thanks in advance for any input.

Andrew

 

[VoIPTools]

This is what I am seeing on my V20 server:

 

[SpeedyPH]

This is what I have also. In V18, whatever I put there, the PBX sends to the trunk provider. In V20, it doesn't matter what I put there, it will still show up as the number listed as the Main Trunk No in the SIP Trunk.

 

[OlegR_3CX]

@SpeedyPH
So you can actually see in the capture/logs that Phonesystem does not send the correct number that you have in the Outbound Caller ID?

 

[VoIPTools]

My guess is the SIP provider is ignoring the passed outbound caller ID and using the SIP provider's assigned caller ID. You can have them do a packet capture to confirm. Talk to your SIP provider.

 

[SpeedyPH]

This goes beyond the 911 settings. No matter what I do, I cannot get the PBX to send out anything other than the main sip trunk number. I have 7 numbers assigned to the sip trunk and no matter where I put any of the other six numbers as the outbound caller ID 3CX will not send that number to the sip provider. I am using the exact settings in 3cx and the sip trunk provider as a PBX on version 18 that works as expected.

The logs at the sip trunk provider are showing that it's receiving the number listed as the main sip truck number in 3CX I can change that number and it will change at the sip trunk provider. I can even change it to a number not with that provider and it will work.

 

[SpeedyPH]

@SpeedyPH
So you can actually see in the capture/logs that Phonesystem does not send the correct number that you have in the Outbound Caller ID?

I can't find the events log on V20. I see where I can set the level of logging but that's it. I feel like version 20 was not ready for release. It seems like there's an awful lot missing.

 

[OlegR_3CX]

@SpeedyPH
Event logs are in the main Dashboard, but not the Activity log and it will be back in one of the future updates.

 

[SpeedyPH]

@SpeedyPH
Event logs are in the main Dashboard, but not the Activity log and it will be back in one of the future updates.

Where do I figure out why the system is only sending out the main trunk DID?

 

[SweetAction]

Do you have a DID set on the outbound rules page?

 

[SpeedyPH]

Do you have a DID set on the outbound rules page?

No

 

[OlegR_3CX]

Try to set it to see if it makes a difference, in any case, it's best to see the .pcap capture, and what the Phonesystem sends out.

 

[SpeedyPH]

Try to set it to see if it makes a difference, in any case, it's best to see the .pcap capture, and what the Phonesystem sends out.

That makes no difference. How do I get the pcap and what am I looking for?

 

[OlegR_3CX]

There is no simple answer to the question of what to look for in the capture as SIP basic knowledge is needed.
This guide shows you how to gather the logs as well as capture the network traffic.
Then in the invite from the Phonesystem to the provider, you can see the SIP header(s) (based on your configurations), and if the number is placed in there.

 

[SpeedyPH]

Okay, so I manually modified a line in the trunk template to get CID working the way i need it to. I changed this line to:
<field name="ParameterOut" custom="" parameter="P-AssertedIdentityUserPart">$OriginatorCallerId</field>

Once I made this modification, I am able to specify any CID at the extension level I want. However, anything I put in the outbound rule will not override the CID. So I need to set every extensions CID instead of using the outbound rule. This also causes a problem with the emergency rules. I need to be able to force CID when someone calls 911 and it will not override the extension level CID setting like it has in the past.

Also, with the OB rules, It doesn't look like they are filtering correctly. I put a range of extensions on the first rule and a different range on the second rule and the first rule is always used as the OB rule.