Forum Discussion
Direct Routing Outbound Number
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.
LinusCansbyThanks 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.
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.
ChykeM Probably not the Caller ID Policy since you can only set a Service number provided by Microsoft here, not a Direct Routing number manged in the SBC.
LinusCansbyGood point. Guess I was looking at this from our POV, where we also considered porting in our own Service Numbers for our Auto Attendants.
Thanks!
ChykeM Thanks for the idea, but as pointed out before ^ the caller id setting is set to "User's number".
LinusCansby 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!
