Hi All,
I have a requirement to disable the call history on a selected amount of 7841
handsets.
To start with the call history has now been moved under the services button and
not the directory’s button.
I know I can disable the logged calls under the line settings and this stops
all received
Hi Matt,
Just tested on our 7841 (sip78xx.10-1-1-9) by sending Init:CallHistory using
PhoneView and it worked fine.
Error 4 is usually an authentication Error, if you are pushing (HTTP POST) the
CiscoIPPhoneExecute object to the phone I suspect their is something wrong with
the Authentication
Ok,
Thanks for the pointer Steven, I have now kind of got this working on the Idle
URL, but after the phone request the idle URL the phone is stuck in the
following state until I go off hook. The Cancel softkey button doesn’t seem to
do anything
[cid:image002.png@01CF4375.4DDDCD50]
It has req
You could try adding a “Init:Services” ExecuteItem after the Init:CallHistory
to see if that closes the page, assuming that it has pulled/parsed the page
correctly and just needs to close the Services page.
On 19 Mar 2014, at 13:33, Matthew Collins
mailto:mcoll...@block.co.uk>> wrote:
Ok
Ok,
I know they aren't support as yet but we have been told that you can
configure CME to think these are a supported handset, but for the life
of me I can't get it to work.
this has come about as Cisco have eol 69XX series and someone spec'd these.
This is the link we have been given which is
Wrapping up on this one...
The SIP Stack error below occurred because CUCM (as the UAS) received an UPDATE
request before receiving a PRACK for its 183 w/ answer. Possible solution is to
have CUCM send a Require: 100rel in the 183 answer, forcing the UAC to PRACK
before sending the update, but
There's a defect for the old license files triggering the grace period error.
There's another one for the CLI command to delete licenses not working, so I'm
glad you didn't hit that one :)
But yes, since the licenses are included in the backup when you did your second
restore it stuck the old
I think I'm making this more complicated than it needs to be.
I have CER 10.
All of our inbound caller IDs from the PSTN are E.164 formatted.
+13125551212 for example.
When configuring the ERL, this is not a problem. I can enter +13125551212
for the ELIN. My translation patterns strip the +1 a
Thanks Ryan. I knew I was pushing my luck with doing multiple restores, so I'm
really glad it worked out. I was ready to start from scratch.
Lelio
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519‐824‐412
Answered my own question. I made it much more complicated in my mind than
it really is.
On Wed, Mar 19, 2014 at 10:54 AM, Erick Wellnitz wrote:
> I think I'm making this more complicated than it needs to be.
>
> I have CER 10.
>
> All of our inbound caller IDs from the PSTN are E.164 formatted.
Thanks John,
It only looks like one bug, which wouldn't affect us.
CSCum96822
3
Grow fails to update expanded system to same version as source system
Cheers,
Tim
From: John Parduhn [mailto:pard...@gmail.com]
Sent: Tuesday, 18 March 2014 10:40 AM
To: Tim Smith
Cc: cisco-voip@puck.nether.net
Sweet! Thanks, Tim.
John
On Mar 19, 2014 3:53 PM, "Tim Smith" wrote:
> Thanks John,
>
>
>
> It only looks like one bug, which wouldn't affect us.
>
>
>
> CSCum96822
>
> 3
>
> Grow fails to update expanded system to same version as source system
>
>
>
> Cheers,
>
>
>
> Tim
>
>
>
> *From:* John
Update –
Well, I finally bit the bullet and stood up a MS AD domain in my lab.
I integrated CUCM into the LDAP and imported the users from LDAP
I also stood up a DNS server.
I reconfigured CUPS to the new domain, joined all of the endpoint
laptops to the
H ... CUPC is old tech . Let me fire up the not-so-way-back machine.
Device and client control almost always comes down to an ownership issue
1. End User has Standard CTI Enabled privilege
2. User owns the Client Services Framework profile
3. User owns the actual phone (unless just
Hey all,
Back on this testing for MRA on Collab Edge... I’ve run up Wireshark on the
computer that I signed in on.
When I establish a call to mobile, or the MCU from the Internet I can see that
my destination address is the PRIVATE IP of the Expressway Edge.
The Expressway E is configured with
Just to clarify, normal inbound/ outbound video calls work.
The Expressway does not have the Dual Network Interface option key.
Cheers
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Dana
Tong
Sent: Thursday, 20 March 2014 2:14 PM
To: Jason Aarons (AM); Ki Wi; Cisco V
The SDP in the logs appears to show :
C = IN IP4 192.168.x.x
I’ve emailed my Cisco rep to see if he can get me a demo option key for the
Dual Network Interface option so I can try the Static NAT config on the VCSE.
From: Dana Tong
Sent: Thursday, 20 March 2014 3:21 PM
To: Dana Tong; Jason Aaro
17 matches
Mail list logo
