Avaya Forwarding/Twinning configuration marked as "to be blocked" per new Canadian CRTC po

[TigerWoods33]

We use Bell as our SIP provider and they have recently provided us with a report of calls that would be marked as "blocked" per the new CRTC policy being enforced in Canada.
All of our regular outbound calls are configured properly, but it looks like we have some issues with forwarding/twinning users showing up on the "blocked" report.

We have Avaya IPO R11 SP1.

We use 9 for "line out" so naturally that is the first digit we tell our users to add in front of their mobile numbers for forwarding/twinning.
Because of how slow the report is taking by Bell to give us results...
A) Has anyone configured their systems (including forwarding/twinning) to be ready for this policy being enforced?
B) Is there a way to track the outbound CLID being sent to Bell on our SIP Trunk so that I could actively complete tests?

Thanks!

 

[Nortel4Ever]

I'm in Edmonton and have never heard of this. What new CRTC policy are you referring to???

 

[janni78]

Have you tried tracing what you actually send to the provider during twinned calls?

Depending on the service provider they use different fields to verify billing, usually Diversion or PAI.

"Trying is the first step to failure..." - Homer

 

[Nortel4Ever]

Is this what you are referring to?
From the way I read this as long as your IPO is providing a valid outgoing number on forwarded/twinned calls there won't be a problem.
In answer to Question B - you should be able to use Monitor to see what outgoing CLID is being sent.


The Canadian Radio-television and Telecommunications Commission (CRTC) has ordered all telecom providers to implement a system to automatically block calls by December 19th, 2019. Specifically, the CRTC requires that the system target calls with caller ID that either “exceeds 15 digits or does not conform to a number that can be dialed (for example, 000-000-0000).” These calls must be blocked before reaching the subscriber. Providers that already offer call-filtering services are exempt from this requirement.

Read more at MobileSyrup.com: CRTC orders telecoms to block customers’ incoming nuisance calls by December 2019

 

[TigerWoods33]

@Nortel4Ever
Yes that is what I am referring too.
Our outgoing numbers are fine for all regular calls, but for some reason Bell is providing us with a report that is pointing to users with invalid PAI's. (It is showing up as the extension rather than the proper outgoing number that is configured in the user's SIP tab of IPO.)
In regards to "B", Monitor seems to be disagreeing with what Bell is providing us on our report. I can try again just to verify, but from what I recall, nothing stood out to me.

@Janni78 How would I go about tracing this? I have setup traces in the SBC thinking that would help me, but it just gives me a useless PCAP file that I cannot use for anything.

 

[d00ner62]

I had opened a ticket with Avaya for this. They do not have a fix for this and they asked that I submit a GRIP request to have this worked on.

For now, the work around is to make changes to every single users SIP tab and put in either their DID if they have one, or the Main number of the company. That way when the extension to extension calls go out to a twinned cell phone, it wont A)show the 3 digit extension as the caller ID (old way) OR B) block the call now that the new regulations are instilled.

 

[janni78]

You should always put a DID in the SIP tab

"Trying is the first step to failure..." - Homer

 

[Travis Harper]

As janni78 said, go the users/sip tab and enter the 7 or 10 digit phone number in there that you want to publish when sending the outbound call. This works is the sip trunk line is set to use internal data.

This adheres to the new CRTC rules in Canada, and calls will complete.