I have seen this twice and I just had to use a third party PDF printer, couldn't get the Microsoft one to work again. Both machines where on the latest Windows 10 version when it happened, so maybe a version update could bring it back.

Skyetell sends an 11 digit number so basically your number with a 1 added by default unless you change it to send only 10 digits your inbound route is missing a one.

14029733266

@scottalanmiller said in Take Flight with Scott Alan Miller: Grand Tour of Europe 2:

Ordering a new microphone to make voice overs better and easier. And looking to attempt switching from OpenShot to KdenLive to see if it is more powerful before the next episode.

You can also try using Davinci Resolve and even Blender

@krisleslie said in XenServer gave error I'm not familiar with:

@krisleslie while I may agree with you on using an SSD, there isn't a point as each are storage mediums. The host loads most of the data in ram which again means kinda doesn't matter the device unless you start talking about usb 2 and usb 1 devices. I use usb 3 which doesn't have any problems with previous-generation tech. Lastly, as far as I recall all storage mediums break unless things have changed...

Quote error?

@dave_c Lucid link seems to be super interesting really.

Found the issue and fixed it.

There were some extra entries in the default pjsip profile which were the culprit. The entries were there since quite a few versions back and hadn't caused any sort of issue with the trunks until we updated yesterday. Even after reverting to the previous working version, the trunks wouldn't get properly created until I found the extra entries and removed them. After that, the endpoints are created and the trunks are up once again.

Getting a strange issue, with my PJSIP trunks all of a sudden. They are SKyetel pjsip trunkgs and they have been working perfectly fine for the last weeks but all of sudden I get the following in the logs:

[2020-03-04 14:33:47] WARNING[16477] res_pjsip_endpoint_identifier_ip.c: Identify 'bf' points to endpoint 'bf' but endpoint could not be found

If I do a pjsip show endpoints in the cli the trunk is not there. As if no trunk was configured, nothing I seem to do makes me be able to recover the ability of the trunk to properly create a pjsip endpoint and the trunk is basically completely down.

Anyone seen something like this before

@LilAng Yep, but nobody reads my wiki guide

Totally agree, the phones suck, but they are what the client has as they didn't want to upgrade to new phones

7 Cisco SPA504G phones on which we are having a strange issue. The line keys for the BLF's are set like this:

Parking lots are 471 and 472 so both keys set let below

Extension: Disabled
Share Call Appearance: private
Extended Function: fnc=sd+blf;[email protected]$PROXY;[email protected]

Attendant Console is properly set as Asterisk Server type on the phone

With the config abouve, If a call comes in user can park the call directly to the slot they want and pick it up without problem, but the issue starts when someone wants to REPARK the call. The second time a call tries to get parked, the phone just puts the call on regular HOLD for some reason and there is no way with the line keys to park the call.

Anyone have an idea about how to fix this behavior?