Apr 23 2020 01:29 AM
Apr 23 2020 01:29 AM
We are currently testing Teams calling with the anticipation of using it productively for the whole company.
The setup with the sbc and users was successfull.
However: When a user dials out to a external PSTN number, the person receiving the call only sees the default number from the SBC and not the user number.
Ex. User A with number +123456789 dials out to User B (external number) +987654321
The User B now sees the default number set on the sbc (ex. +123456780) instead of the User A number.
Thanks for your help.
Apr 23 2020 01:37 AM
@Lars_Nestler The default number on the SBC? Is that a configuration you have done in your SBC to replace the Caller number with this default number? If you don't have any rules in your SBC to change the caller number it should show the number of User A.
Do some tracing on your SBC and see what you send out to your operator, so that you send out the correct number in the SIP INVITE. It could be your ITSP that changed this number for you.
Apr 23 2020 05:14 AM
@Linus CansbyThanks for your fast answer.
We are hosting our SBC from an external provider. In the admin portal for the SBC we can setup a fixed display number for the whole SIP Trunk, but we can also configure it to take the information from the call / teams.
I have emailed our sbc provider and asked them about this case. Sadly I can't trace a call on the sbc as we do not have access to it (other than the admin web portal). I've already looked into tracing a call from my local machine, but the whole traffic is encrypted (as should be).
I will await the answer from our sbc provider and update this thread.
Apr 23 2020 01:24 PM
Did you check your Caller ID Policies in the Teams Admin Center? If you login to the Teams Admin Center, under Voice -> Caller ID Policies... Check you Global policy to see what it is set to. The options here are to use the "User's number", use a "Service Number" or set to "Anonymous". If it is already set to User's Number or Anonymous, but still showing a different number, then there is most likely a Transformation Rule on the SBC that's setting that number for you. We also have Direct Routing for my company, and I purposely setup this exact same Transformation Rule on our SBC, so that all outgoing calls show the company's Primary Number. The rule would look something like the following on the SBC:
Match Type: Optional (Match One)
Input Field Type: Calling Address/Number
Input Field Value: \+?(.*)
Output Field Type: Calling Address/Number
Output Field Value: <The number you want as Outgoing Caller-ID>
Hope this helps.
Apr 30 2020 06:09 AM
@ChykeM Thanks for the idea, but as pointed out before ^ the caller id setting is set to "User's number".
@Linus Cansby As far as the sbc provider is concerned, it looks like teams doesn't include the callerid in the sip call. Because of that the sbc chooses the "default" number of the call.
Are there any other settings which have to be taken in account in regards to this problem?
I have changed the -ForwardPai setting of the sbc to $true, but this still didn't help.
Does anyone have any other ideas?
Thanks a lot!
May 17 2020 11:39 PMSolution
Alright, I have found the answer.
We had our direct routing numbers configured as: tel:+12345678900;ext=900 so that the user see's his / her internal extension in teams.
This however, sent out the whole number (as shown above) in the "FROM" address of the SIP package.
Our SBC was then not able to translate that number (as there were letters) and set the number to the default fallback one.
Hope this helps others, who might have the same issue.