Erwin Bierens Blog

Knowledge is Power

Microsoft Teams account broken

2020-10-06 1 min read Microsoft Teams "Erwin Bierens"

How the provisioning works succesfully

By default for a pure Online user the Default state will be:

    InterpretedUserType : PureOnlineSfBUserWithTeamsLicense

Powershell Lookup

    get-csonlineuser user@microsoftteams.nl |FL SipAddress, InterpretedUserType, TeamsUpgradeEffectiveMode, EnterpriseVoiceEnabled

When you Assign Enterprise Voice and a LineUri the status will change to:

    InterpretedUserType : PureOnlineSfBUserWithTeamsLicenseNeedsProvisioningToAD

This will change to:

    InterpretedUserType : PureOnlineSfBUserWithTeamsLicenseNeedsPublishingToAAD

And finally this should result back in normal status:

    InterpretedUserType : PureOnlineSfBUserWithTeamsLicense

When this status ends in:

Direct Routing keeps sending Anonymous

2020-10-05 1 min read Microsoft Teams "Erwin Bierens"

Problem

While i was configuring an Audiocdes SBC with Direct Routing setup and started testing, we faced the issue that every call outgoing is presenting Anonymous as caller ID.

Anonymous

When looking up the SDP invite i saw the parameter Privacy showing up. Privacy ID

Solution

After some digging, i found that the Privacy ID is added automatically when you enable the option -forwardPAI $true (P-Asserted-Identity) within the Set-CsOnlinePSTNGateway cmdlet.

Because i don’t want to remove the PAI, i created the following manipulation rule in the Audiocodes SBC to remove the Privacy ID. Action Subject:

Setup and Create Audiocodes log files

2020-07-16 1 min read Audiocodes "Erwin Bierens"

First start with downloading the Audiocodes Syslog viewer click here. Install Audiocodes “syslog viewer” on a windows-based PC.

Enable Syslog : enable
Syslog Server IP Address : IP of the computer where the Audiocodes Syslog viewer is installed.
Syslog Server Port : 514
VoIP Debug Level : detailed

audiocodes settings

Start the Audiocodes syslog viewer and click on the play button to start the capture.

Audiocodes Mediant running out of media legs

2020-03-06 2 min read Audiocodes "Erwin Bierens"

14:06:01.249 10.64.41.34 local0.warn [S=42600819] [SID=3b46e2:175:548977] ( lgr_psbrdex)( 88228952) !! [ERROR] BoardInterface::AllocateLocalAddresses failed since cpCMediaRealmMgr encountered an error for realm 1 [Time:09-12@14:06:01] 14:06:01.249 10.64.41.34 local0.warn [S=42600820] [SID=3b46e2:175:548977] ( lgr_flow)( 88228953) !! [ERROR] (#435)ChannelResource::AllocateMediaIpPorts failed to allocate Media Resources [Time:09-12@14:06:01] 14:06:01.249 10.64.41.34 local0.warn [S=42600821] [SID=3b46e2:175:548977] ( sip_stack)( 88228954) ?? [WARNING] SBCSDPSession(#375)::HandleOfferSDPFromIP - Failed to Allocate Media IP Port [Time:09-12@14:06:01] 14:06:01.249 10.64.41.34 local0.notice [S=42600822] [SID=3b46e2:175:548977] ( lgr_stk_ses)( 88228955) SBCOfferAnswerMngr(#375) - OfferAnswerCompleted not in SIP_MEDIA_COMPLETED state. Returning to previous state: SIP_MEDIA_IDLE [Time:09-12@14:06:01] 14:06:01.249 10.64.41.34 local0.notice [S=42600823] [SID=3b46e2:175:548977] ( sip_stack)( 88228956) New SIPMessage created - (#303) [Time:09-12@14:06:01] 14:06:01.249 10.64.41.34 local0.notice [S=42600824] [SID=3b46e2:175:548977] ( lgr_flow)( 88228957) | |(SIPTU(#835)DISCONNECT_REQ State:Invited(SDf4upe01-d1603abe001c919606631f9c74cd598f-a0gt3u3010) [Time:09-12@14:06:01] 14:06:01.249 10.64.41.34 local0.notice [S=42600825] [SID=3b46e2:175:548977] ( lgr_flow)( 88228958) —- Outgoing SIP Message to 62.59.93.4:5060 from SIPInterface #1 (SIP_Tele2) UdpTransportObject(#1)-UdpSocketAPI(#1) —- [Time:09-12@14:06:01] 14:06:01.249 10.64.41.34 local0.notice [S=42600826] [SID=3b46e2:175:548977] SIP/2.0 488 Not Acceptable Here Via: SIP/2.0/UDP 62.59.93.4:5060;branch=z9hG4bKn7pom200a0mf3a93drs0.1 From: sip:+31611369530@vcas1.voip.tele2.nl;user=phone;tag=SDf4upe01-725377305-1575896761237- To: sip:+31880430430@10.32.35.130;user=phone;tag=1c922444566 Call-ID: SDf4upe01-d1603abe001c919606631f9c74cd598f-a0gt3u3010 CSeq: 895623627 INVITE Server: Mediant 3000/v.7.00A.136 Reason: SIP ;cause=488 ;text=“488 Not Acceptable Here” Content-Length: 0 [Time:09-12@14:06:01]

No RingBack when using Microsoft Teams Direct Routing

2019-10-25 3 min read Microsoft Teams "Erwin Bierens"

Recently we have decomissioned our Microsoft Cloud Connector Edition and migrated most of our telephony users to Microsoft Teams with Direct Routing. One big issue we faced was that when a external caller called us by PSTN, they only heard one RingBack tone followed by deadly silence till someone picked up or landed in Azure VoiceMail. I Kill You

Thanks to my friend Goos Stuut, working at our local distri for Audiocodes we found out what was happening and we solved this issue.

Deploy error Skype for Business Cloud Connector - CredSSP

2018-10-09 2 min read Audiocodes Skype for Business Skype for Business Online Erwin Bierens

The problem

Last week i ran in to some errors while re-deploying a Cloud Connector, Changed some settings in the INI and while starting the redeploy gave me the following error:

	`Preparation phase started...
	The configuration file for Cms server setup is generated in C:\Users\Administrator\CloudConnector\ApplianceRoot\Instances\2.1.0\ExportedConfig\ServerConfig-Cms.ini.
	Preparation phase finished.
	Deployment phase started...
	Enabling credential delegation for NTLM on host machine.`
	`
	#text : false
	#text : true
	#text : true
	#text : false
	#text : true
	#text : Relaxed`


		[192.168.214.3] Connecting to remote server 192.168.214.3 failed with the following error message : The request is not supported. For more information, see the about_Remote_Troubleshooting Help topic.
		+ CategoryInfo          : OpenError: (192.168.214.3:String) [], PSRemotingTransportException
		+ FullyQualifiedErrorId : 50,PSSessionStateBroken
		[192.168.214.3] Connecting to remote server 192.168.214.3 failed with the following error message : The request is not supported. For more information, see the about_Remote_Troubleshooting Help topic.
		At C:\Program Files\WindowsPowerShell\Modules\CloudConnector\Internal\MtSetup.ps1:294 char:13
		+             Invoke-Command -ComputerName $machineIP -Credential $doma ...
		+            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		+ CategoryInfo          : OpenError: (192.168.214.3:String) [], PSRemotingTransportException
		+ FullyQualifiedErrorId : 50,PSSessionStateBroken
		Trying to exit current manual maintenance mode.
		Successfully exit manual maintenance mode.
		[192.168.214.3] Connecting to remote server 192.168.214.3 failed with the following error message : The request is not supported. For more information, see the about_Remote_Troubleshooting Help topic.
		At C:\Program Files\WindowsPowerShell\Modules\CloudConnector\Internal\MtSetup.ps1:294 char:13
		+             Invoke-Command -ComputerName $machineIP -Credential $doma ...
		+            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		+ CategoryInfo          : OpenError: (192.168.214.3:String) [], PSRemotingTransportException
		+ FullyQualifiedErrorId : 50,PSSessionStateBroken`

After some diging in to this problem i found some people having same issues with other Microsoft products. Last March Microsoft released the CredSSP update and this prevented connecting to vulnerable systems using older authentication methods.

Common Area Phones - Skype for Business Online

2018-03-30 1 min read Skype for Business Online Erwin Bierens

Microsoft has enabled a new service called “Common Area Phone”, this way you can enable IP Phones as a generic device. The “Common Area Phone” License contains:

Phone System
Skype for Business Online (Plan 2)

Let’s create a user

I’m creating a IP Phone for my living room.

Make sure you assign the Common Area Phone license.

Now the user is created boot up the IP Phone.

Older posts Newer posts