SOLVED

Direct Routing SIP signaling FQDNs

%3CLINGO-SUB%20id%3D%22lingo-sub-2599980%22%20slang%3D%22en-US%22%3EDirect%20Routing%20SIP%20signaling%20FQDNs%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2599980%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-plan%23sip-signaling-fqdns%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-plan%23sip-signaling-fqdns%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20above%20document%20has%20been%20updated%20recently%20and%20it%20states%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EThe%20FQDNs%20%E2%80%93%20sip.pstnhub.microsoft.com%2C%20sip2.pstnhub.microsoft.com%20and%20sip3.pstnhub.microsoft.com%20%E2%80%93%20will%20be%20resolved%20to%20IP%20addresses%20from%20the%20following%20subnets%3A%3C%2FEM%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CEM%3E52.112.0.0%2F14%3C%2FEM%3E%3C%2FLI%3E%3CLI%3E%3CEM%3E52.120.0.0%2F14%3C%2FEM%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20when%20you%20do%20a%20nslookup%20for%26nbsp%3Bsip.pstnhub.microsoft.com%2C%20sip2.pstnhub.microsoft.com%20and%20sip3.pstnhub.microsoft.com%2C%20none%20of%20them%20resolve%20to%20any%20of%20the%20above%20subnets.%20I%20distinctly%20remember%20previously%20the%20list%20of%20IP%20address%20used%20to%20be%3C%2FP%3E%3CP%3E52.114.7.24%2C%2052.114.132.46%2C%2052.114.75.24%2C%2052.114.76.76%2C%2052.114.148.0%2C%2052.114.14.70%2C%3C%2FP%3E%3CP%3E52.114.16.74%2C%2052.114.20.29%2C%2052.112.0.0%2F14%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ECan%20someone%20from%20Microsoft%20clarify%20this.%20I%20don't%20see%26nbsp%3B52.114.x.x%20subnet%20in%20the%20documentation.%26nbsp%3B%3CBR%20%2F%3EThanks%2C%3C%2FP%3E%3CP%3E-Balaji%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2599980%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDirect%20Routing%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2600161%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20SIP%20signaling%20FQDNs%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2600161%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3788%22%20target%3D%22_blank%22%3E%40Balaji%20NJL%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESee%20here%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fcommunication-services%2Fconcepts%2Ftelephony-sms%2Fsip-interface-infrastructure%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAzure%20direct%20routing%20infrastructure%20requirements%20-%20Azure%20Communication%20Services%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20FQDNs%20%E2%80%93%20sip.pstnhub.microsoft.com%2C%20sip2.pstnhub.microsoft.com%2C%20and%20sip3.pstnhub.microsoft.com%20%E2%80%93%20will%20be%20resolved%20to%20one%20of%20the%20following%20IP%20addresses%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CCODE%3E52.114.148.0%3C%2FCODE%3E%3C%2FLI%3E%0A%3CLI%3E%3CCODE%3E52.114.132.46%3C%2FCODE%3E%3C%2FLI%3E%0A%3CLI%3E%3CCODE%3E52.114.75.24%3C%2FCODE%3E%3C%2FLI%3E%0A%3CLI%3E%3CCODE%3E52.114.76.76%3C%2FCODE%3E%3C%2FLI%3E%0A%3CLI%3E%3CCODE%3E52.114.7.24%3C%2FCODE%3E%3C%2FLI%3E%0A%3CLI%3E%3CCODE%3E52.114.14.70%3C%2FCODE%3E%3C%2FLI%3E%0A%3CLI%3E%3CCODE%3E52.114.16.74%3C%2FCODE%3E%3C%2FLI%3E%0A%3CLI%3E%3CCODE%3E52.114.20.29%3C%2FCODE%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EHope%20that%20answers%20your%20question%20%3AD%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%20Chris%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2600651%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20SIP%20signaling%20FQDNs%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2600651%22%20slang%3D%22en-US%22%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3E%20for%20your%20quick%20reply.%20Yes%2C%20these%20are%20the%20IPs%20I%20had%20originally.%20Even%20though%20both%20document%20got%20updated%20on%2006%2F30%2F2021%2C%20the%20IP%20address%20list%20seems%20to%20be%20incorrect%20on%20the%20one%20that%20I%20referred.%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#sip-signaling-fqdns

 

The above document has been updated recently and it states 

 

The FQDNs – sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com and sip3.pstnhub.microsoft.com – will be resolved to IP addresses from the following subnets:

  • 52.112.0.0/14
  • 52.120.0.0/14

 

But when you do a nslookup for sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com and sip3.pstnhub.microsoft.com, none of them resolve to any of the above subnets. I distinctly remember previously the list of IP address used to be

52.114.7.24, 52.114.132.46, 52.114.75.24, 52.114.76.76, 52.114.148.0, 52.114.14.70,

52.114.16.74, 52.114.20.29, 52.112.0.0/14


Can someone from Microsoft clarify this. I don't see 52.114.x.x subnet in the documentation. 
Thanks,

-Balaji

 

4 Replies

@Balaji NJL 

 

See here

 

Azure direct routing infrastructure requirements - Azure Communication Services | Microsoft Docs

 

The FQDNs – sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com, and sip3.pstnhub.microsoft.com – will be resolved to one of the following IP addresses:

  • 52.114.148.0
  • 52.114.132.46
  • 52.114.75.24
  • 52.114.76.76
  • 52.114.7.24
  • 52.114.14.70
  • 52.114.16.74
  • 52.114.20.29

Hope that answers your question :D

 

Best, Chris

 

Thanks @Christopher Hoard for your quick reply. Yes, these are the IPs I had originally. Even though both document got updated on 06/30/2021, the IP address list seems to be incorrect on the one that I referred.
best response confirmed by Balaji NJL (Occasional Contributor)
Solution
You may want to check a subnet calculator
52.112.0.0/14 contains 52.112.0.0 - 52.115.255.255
It includes the 52.114.x.x range.

You are right, I didn't realize /14 covers 52.114.x.x. Thanks for pointing it out.

www.000webhost.com