SIP Authirzation header needed to be in the first REGISTER request

[Halsser]

I have an SIP trunk to an ITSP, and it’s not registering because the provider requires the Authorization SIP header to be included in the first REGISTER request, which Cisco routers don’t do by default.

My provider has security and DDoS rules that drop any traffic without the Authorization SIP header, without responding to the sender.

From my understanding, the Cisco router first tries registration without authorization. When it receives an "Authorization Required" message, it then re-registers, including the Authorization header in the new REGISTER request. However, my issue is that my provider does not respond with an "Authorization Required" message. Instead, it simply drops the first registration request because it does not include the Authorization header.

My question is, is there any workaround to force the Cisco router to include the Authorization header in the first REGISTER request sent to the ITSP? 

My sip trunk config looks like this:

voice class tenant 2

registrar dns:ABC.com expires 3600

sip-server dns:ABCD.com

credentials username 2025 password 6 PASSWORD  realm ABC.com

authentication username 2025 password 6 PASSWORD realm ABC.com

connection-reuse

 bind control source-interface GigabitEthernet1/1/1

 bind media source-interface GigabitEthernet1/1/1

I need something like this Authorizations header to be in the first register request message:

Authorization: Digest username="2025", realm=" ABC.com",uri="sip: ABC.com:5060", response=" ", nonce=" 

[Roger Kallberg]

Other than adding it to the outbound invite with a SIP profile I don’t know how you could do that. The process that the router does this is per the defined SIP standards, so what your service provider is doing is outside of standard operation from what I know. With that I think it would be hard, if not impossible, to do this other than using a SIP profile that adds the outlined fields to the invite as one of the big use cases for SIP profiles is to handle interoperability between disparate systems.

If you post the entire SIP dialog in an attached text file it would be easier to help you out with crafting a SIP profile that could do this.

[Roger Kallberg]

Thank you. One thing, a SIP dialogue is the entire SIP messages collection, not just one message.

[Mohamed H. Abdelmotaleb]

Please read the following document, you can force the phone to send register request to CUBE first then the CUBE asked for authorization  then the CUBE can send the first register message with authorization header.

https://www.cisco.com/c/en/us/td/docs/ios/ios_xe/voice_cube_-_ent/cube-ent_wip/cube_tips/cube_sipsip/fts-11097_boron.pdf

[Halsser]

Thank you @Mohamed H. Abdelmotaleb , my case is Cisco CUBE SIP TRUNK TO ITSP