Cisco 7970 and 3cx - It works :)

[mfaster]

DTMF Tones working on 7970

Ok I my bad. DTMF tones work on 7970. I needed to set the Grandstream GXW4104 gateway to use RFC-2833 for DTMF signaling. I am using the vanilla cnf.xml config files for the 7970.

 

[Wardy]

Does anyone know where I can get the SIP firmware for a Cisco 7970

Stephen

 

[StewartGilray]

hi,
We've just got a 7970 and it has FW SIP70.8-5-2SR1S on it...

Whilst I've followed the above EXACTLY (other than FW) we get some side effects...

1. The phone can make calls internally/externally
2. We can call the phone from an internal extension
3. We CAN'T call it from the outside world
4. (Most importantly) according to 3CX it's status is "NOT registered", yet user status is "Available"

HELP!??!

I've spent since 10am yesterday on this and I'm completely bemused. I've tried 3 different FW (inc. latest 9.3) I've tried different suggested CFG files (one of which completely borked the clock on the phone).

So really am at the end of my tether...

Stewart

 

[lneblett]

A few things -

1. This is not an officially supported phone. Not to mean that it will not work or can't be manipulated to work, but more in keeping with the idea that it may not work and/or that the experience with how to get it to work may be limited with the userbase. The forum thread that you have used is from a number of years ago and much may have changed in the interim.

2. The phone needs to be registered. If not, then the system will invoke the associated rules for that extension being unregistered (as you have described the scenario). A look at the logs may reveal if the phone is even attempting to register and if so, what about the registration process it doesn't like.

3. Do not confuse the phone status of being registered or not with the user status. One (phone or extension) is an indication of how the system sees the physical presence of a connection while the other is merely an indication of what the user's status is so that custom call handling routines can be accommodated. User status takes precedence. In this manner, if a user were "out of office", then the rules established for this aspect will be invoked rather than the ones fthat migt be established for "busy" or "unregistered". I don't think you want the system to automatically override the user's desired call handling should a phone become unregistered for some reason.

 

[StewartGilray]

Thanks for the reply, what do you recommend for my next step?

 

[lneblett]

Step 2. Take a look at the Activity and Event logs and see if any attempt to register is detected.

If so, then see if you can determine the cause of why 3CX does not like, Most of the time it will be a credential issue (user id, auth id and/or password) ultimately resulting in the IP of the phone being blacklisted for too many attempts.

If not, then make a call to a system extension (*777 echo, VMail, IVR, or other) and post the results of the log. You indicated you could make internal to internal.

If not, then make a call using an external phone to the extension of interest. My guess here is that the unregistered rules will be invoked, but you never indicated what the repsonse was. You simply indicated that you could not call, but what actually happened - nothing, call forwarded, vmail, message from system indicating?????

 

[StewartGilray]

Sorry, been busy launching a product via Steam last night ...

I've not tried this lot yet, but will soon, in the meantime, the calls went to Voicemail.

 

[netswork]

Dion,

Where you able to, or have you tried to get a blf working on the 7970? Nice work by the way.

 

[Hornett]

Update:

I've had a stab at trying to get this working.

So far I have configured 3 7970s which have all authenticated with 3cx.
My next hurdle is that when i attempt to dial either extensions configured on the 3 handsets, i am denied with a busy tone.

I am unsure as to why this is the case though here is a copy of my 3cx service status log.

00:00:12.541 CallConf:nIncoming Can not resolve target for call from "Dion Ignacio"<sip:[email protected]>;tag=001243d1defa00031e594670-e327c1fe to <sip:[email protected];user=phone>
00:00:12.541 CallConf::Rejected Call (C:14) is rejected: Target is not resolved
00:00:12.491 CallConf:nIncoming Incoming call from Ext.100 to sip:[email protected]
23:59:47.746 ServRegs:nAdd Registered: Ext.102
23:59:33.796 ServRegs:nAdd Registered: Ext.100
23:59:20.026 ServRegs:nAdd Registered: Ext.101

Can anyone shed some light on the issue ?

Cheers,

Dion

Not sure if you resolved this, but it looks like you're missing the cisco_dialplan.xml file on the phone, which sets the intra-digit timing. without that, it defaults to 0, so you dial the first number pressed.