Search results for query: *

I know right, I had similar concerns especially when i saw that the PRI was configured as a standard T1 I was sure I read somewhere that it would not work unless PRI but maybe the spec is the hardware because it is a PRI card in the cabinet config (confirmed photo). Oh well, I'm not gonna...

Ok, yay I got the s/w and I'm connected. Here's what I did. 1) I created a new portable station (unregistered of course) and set COS 1 (has CO fwd enabled) and set CF ALL w/ 9+1+AC+Number 2) I set DID DAY/NIGHT etc to new portable station number Works like a charm! -Phil Ingram...

Thanks for the info and you are correct it does not have a D at the end, that was a typo and I've corrected the original post =) I have VARs I work with that are dealers, I can get the s/w thanks for confirming I DO need the US version. -Phil Ingram http://www.tellatek.com/ - VOICE | DATA | DESIGN

I think the issue is not having the US version of the MC s/w. It now reports an error when connecting "program not installed correctly" so I know the default password and USB drivers are good. If I choose the wrong system or try a different password I get a completely different error so at...

Thanks for the great info. One thing that seems to be of insider knowledge is during the s/w installation it asks for a suffix code, i.e. KXTDA100XX where XX is AG, BR, CE...etc. I couldn't find anything in the manuals nor photos the client sent me. How important is this for the s/w to work...

It's been years since I touched a KX but I've been a phone tech for 25+ years and I know my way around just about every major manufacturer out there (NEC, Avaya, Toshiba, Nortel...) and I've been tasked with programming some temporary call forwarding while my client waits for some numbers to be...

Good suggestion MercuryComm, it had crossed my mind that a bad hook switch could result in the off hook alert but in this scenario it's clearly the speakerphone mode that is active which puzzled me because this can't be actived from another station via voice over or paging, etc. The only things...

Maybe...just maybe...the cleaning lady sneaks in and places a call to Guatemala to talk to her distant cousin who only has 4 fingers on his left hand, but that's a different story. She does this every morning, like ritual. Oh yeah, and also sits back in the leather lounge chair with her feet...

ah, I misunderstood. I have worked with a lot of systems and I don't recall one in which you can place a conference call on hold that someone else can pick up when using the systems built in conference feature, however... When using a carriers conference function the system sees you as only...

Ok, just remember that if you can get the carrier tech to try dialing a 418 number from the circuit DMARC using a tester and they have the same ringback issue, they should be obligated to figure out what the problem is. -Phil Ingram http://www.tell-a-tek.com/ {All-You-Can-Eat Telecom and IT Buffet}

LOL! yep. that's got to be the problem! -Phil Ingram http://www.tell-a-tek.com/ {All-You-Can-Eat Telecom and IT Buffet}

The Aspire is much like the IPKII I have been told. I believe the IPKII was developed from the Aspire. I don't have first-hand Aspire experience but I have much on the IPKII. Via the web admin you should be able to go through the caller-id wizard to verify that "caller-id through" mode is...

Ok, let's look at what we have narrowed down. 1 - The issue does not happen on other trunk card/types in the same phone system - i.e. 4COT card w/ analog pots line 2 - The problem only happens to certain LD numbers, not all, but the same results with those numbers 3 - The problem only happens...

You need to change the restriction level to that of another phone that is un/less restricted. see cmd 1201>XXXX>YZ where XXXX is the extension number and Y is the Day restriction level 0-7 and Z is the night restriction level 0-7 typically 0 allows everything and 7 allows only internal...

...tables. Then test using direct trunk access. You can assign a direct access code... 200>A110:110 (110 = route 10) (where the access code is *110 to access route 10 or whatever your PRI route is) Then test the route bypassing LCR by dialing *110+number directly. This will ensure that...

LT15 for a 4 circuit card, I assumed it was an 8 circuit, sorry bout that. Ok, so now you've eliminated the 'called' number being the problem or even specifically your switch no matter what trunk or slot. Are you using LCR, i.e. 200>9>A129? If so... Try a direct access code for the PRI trunk...

I use this setup as well, might I suggest using tenant 63. If you ever have remote pims, you can then use tenants 1, 2, 3 etc. for each site to setup 911 patterns to local loop trunks and then the tenant matches the site number keeping it easy to remember when add/del/move stations around...

OK, so you put the trunk in route 50 and assigned *77 as the access code. It also looks like the card is in slot 07 of the second pim and you connected the co trunk to the second to last circuit on the card? Is this correct? Also by default, your trunk route should be loop start so you should...

...20X is 200 to 203 depending on numbering plan, 200 is default and where Y/YYYY is your access code you'll use, for example A100 would be lifting the handset and dialing *100 to access trunk group 00.) 6) Test your COT -Phil Ingram http://www.tell-a-tek.com/ {All-You-Can-Eat Telecom and IT...

The key is going to be proving to the carrier tech that the problem... #1 only exists when dialing from PRI and... #2 getting trace examples of the issue from the d-channel Upon further inspection, they should be able to diagnose and address the issue by proving which side is the culprit...