Hi, Got a problem with a UC540. Call forwarding does not work to external numbers. That is both CFwdAll set from handsets, call forward on busy set from CCA and manual transfers to external numbers. You just get slow busy. All calls are via SIP. I've attached a cut down running-config. Thanks for any advice, Adam ... View more

Hi, Having a few problems with night service. I'm trying to set it all up using CCA to be compliant, and have attached a screen shot of the relevant screens. To go through how it works: Incoming calls are directed to a floating extension - 210. 210 has a CFWD all to a hunt group 501 which has three members. So far so good! I've then set 210 as a night service extension, with a CFWD night service to 511 - which is a blast group with all phones in it. There is then a schedule (not shown) than switches night service on and off at 17:30 to 09:00. This seems to work. The problems we get are firstly if someone is in early and dials *299 it switches night service off - but the schedule then toggles it back on at 09:00. It seems the schedule is only a toggle, which is a bit daft. Is that correct or should it keep the night service off when switched off? Secondly switching night service off doesn't seem to update all phones, some carry on saying night service on. Although this shouldn't be a problem it leads to other users toggling night service, putting it back on again, and no one knows what it is doing until a call comes in. Any suggestions as to why it is doing that, or feedback on how to set it up better will be welcome. Thanks, Adam ... View more

Hi, I'm trying to get a Quescom Q50 GSM device to talk to an UC540. The Q50 pretends to be an ISDN line and is connected to the UC540 as such, we don't have any real ISDN lines, and any calls to the ISDN are routed by the Quescom as a GSM call. Outgoing calls are working fine. I'm having trouble getting incoming calling working. I've pasted a log sample below. The BAD FRAME errors are apparently because the Q50 doesn't do any CRC. The Q50 is set to pretend any incoming call is coming into 123456, which you can see in the log. I've got an incoming Dial plan set by CCA on the UC540 with the calling ID of 123456 that routes it to a blast group. Dialing on the Q50 gets threee rings then a disconnection. Obviously I've got Quescom looking into this, but would value a second opinion. It would seem the Q50 is behaving correctly, as outgoing calls are fine. Thanksm Adam 012907: May 1 16:03:39.826: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to up 012908: May 1 16:03:40.750: ISDN BR0/1/0 Q921: User RX <- SABMEp sapi=0 tei=0 012909: May 1 16:03:40.750: ISDN BR0/1/0 Q921: User TX -> UAf sapi=0 tei=0 012910: May 1 16:03:40.778: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0 012911: May 1 16:03:40.782: ISDN BR0/1/0 Q921: User RX <- INFO sapi=0 tei=0, ns=0 nr=0 012912: May 1 16:03:40.782: ISDN BR0/1/0 Q931: SETUP pd = 8 callref = 0x1F Bearer Capability i = 0x8090A3 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0x89 Exclusive, B1 Calling Party Number i = 0x80, '07815197604' Plan:Unknown, Type:Unknown Called Party Number i = 0x80, '123456' Plan:Unknown, Type:Unknown High Layer Compat i = 0x9181 012913: May 1 16:03:40.786: ISDN BR0/1/0 Q921: User RX <- BAD FRAME(0x020173) 012914: May 1 16:03:41.778: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0 012915: May 1 16:03:41.786: ISDN BR0/1/0 Q921: User RX <- BAD FRAME(0x020173) 012916: May 1 16:03:42.118: %SYS-5-CONFIG_I: Configured from console by connect on vty0 (192.168.16.18) 012917: May 1 16:03:42.778: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0 012918: May 1 16:03:42.786: ISDN BR0/1/0 Q921: User RX <- BAD FRAME(0x020173) 012919: May 1 16:03:43.770: ISDN BR0/1/0 Q921: User RX <- INFO sapi=0 tei=0, ns=0 nr=0 012920: May 1 16:03:43.770: ISDN BR0/1/0 Q931: SETUP pd = 8 callref = 0x1F Bearer Capability i = 0x8090A3 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0x89 Exclusive, B1 Calling Party Number i = 0x80, '07815197604' Plan:Unknown, Type:Unknown Called Party Number i = 0x80, '123456' Plan:Unknown, Type:Unknown High Layer Compat i = 0x9181 012921: May 1 16:03:43.778: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2 012922: May 1 16:03:43.778: ISDN BR0/1/0 Q921: User TX -> IDVER ri=0 ai=0 012923: May 1 16:03:43.794: ISDN BR0/1/0 Q921: User RX <- IDCKRQ ri=0 ai=0 ... View more

On of the reasons we are looking at Onplus is for the warranty and service contract reporting. We have it running on our network and it reports the following about our UC540: Product is out of Warranty Product Software is no longer supported Contract Details identifies an Active contract - but Full contract information is not available The problem with these are that although the base warranty is over the product is under Prosupport cover, and so has a warranty. This needs to be picked up on, as we don't care about the base warranty when there is a service contract available. Product software is the latest available image (software pack 8.2 contains IOS 15.1(2)T4, 8.6 is due out next month), and it is a current product, so Product Software is no longer Supported is another false positive. Full Contract information is not available is an obvious complaint. Lastly the Cisco Support Phone Number listed are US numbers. We are in the UK, no use to us. Can anything be done about these? Thanks, Adam ... View more

The ConnectWise ticket integration documentation is a bit scant. Automated ticket resolution doesn't seem to work, the tests I've done have just opened another ticket with at resolved status. How does the integration fed back? There doesn't seem to be any uniqueness in the Onplus generated ticket and there aren't any cross references set. Thanks, Adam ... View more

I'm trying to sort something with a UC540 and SPA525G2 handsets. We have a blast group that half the staff are in. Don't want a hunt group - they are too slow to anwer - we like blast groups. We want two things; firstly to be able to log out of the blast group. HLog doesn't work, as it isn't hunt group, and DND is a bit too full on. Secondly we want a way to identify which calls are coming into that blast group as opposed to direct line or other hunt groups so they can be answered accordingly. I've looked at using a seperate shared or overlay button for the blast group, which may be the only way - but it uses up valuable button real estate on the phone. And doesn't solve the log out issue. Any suggestions as to how we can do this welcome! Thanks, Adam ... View more