Allowed non default SipSigPort

%3CLINGO-SUB%20id%3D%22lingo-sub-1676098%22%20slang%3D%22en-US%22%3EAllowed%20non%20default%20SipSigPort%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1676098%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20know%20the%20range%20of%20non%205061%20SipSigPort%20allowed%20for%20Direct%20Routing%2FPSTNGateway%3F%20Suppose%20I%20have%20a%20really%20weird%20situation%20that%20force%20me%20to%20use%20higher%20port%2C%20say%207061%20for%20SipSigPort.%20Is%20that%20still%20allowed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1676098%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDirect%20Routing%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ephone%20system%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1676852%22%20slang%3D%22en-US%22%3ERe%3A%20Allowed%20non%20default%20SipSigPort%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1676852%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F430486%22%20target%3D%22_blank%22%3E%40ghwishnu%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethe%20SBC%20that%20you%20connect%20to%20Teams%20can%20be%20added%20via%20Teams%20Admin%20Center%20or%20PowerShell.%20For%20PowerShell%20the%20command%20would%20be%26nbsp%3BSet-CsOnlinePSTNGateway.%20This%20command%20also%20includes%20a%20paramter%20to%20specify%20the%20SIP%20port%20where%20the%20SBC%20is%20listining.%20This%20is%20SipSignalingPort.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20docs%20say%20for%20this%20parameter%20%22%3CSPAN%3EListening%20port%20used%20for%20communicating%20with%20Direct%20Routing%20services%20by%20using%20the%20Transport%20Layer%20Security%20(TLS)%20protocol.%20%3CSTRONG%3EThe%20value%20must%20be%20between%201%20and%2065535%3C%2FSTRONG%3E.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fskype%2Fset-csonlinepstngateway%3Fview%3Dskype-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ESet-CsOnlinePSTNGateway%20(SkypeForBusiness)%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHope%20this%20helps.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ERegards%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EPaul%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi, 

 

Does anyone know the range of non 5061 SipSigPort allowed for Direct Routing/PSTNGateway? Suppose I have a really weird situation that force me to use higher port, say 7061 for SipSigPort. Is that still allowed?

 

Thanks in advance.

 

2 Replies
Highlighted

Hi @ghwishnu 

 

the SBC that you connect to Teams can be added via Teams Admin Center or PowerShell. For PowerShell the command would be Set-CsOnlinePSTNGateway. This command also includes a paramter to specify the SIP port where the SBC is listining. This is SipSignalingPort. 

The docs say for this parameter "Listening port used for communicating with Direct Routing services by using the Transport Layer Security (TLS) protocol. The value must be between 1 and 65535."

 

Set-CsOnlinePSTNGateway (SkypeForBusiness) | Microsoft Docs

 

Hope this helps.

 

Regards,

 

Paul

Highlighted

Hi @Paul Lange 

Thank you very much for replying. 

 

Well then it should be okay if so. I asked because I cant connect using something like 7061. When moving to other more opened network to test, still cant connect to 7061, but 5061 - 5081 work just fine. Now I am sure this is something else along the path. 

 

Thank you again for the clue.