Speed Dial "Not Acceptable"

[TSlocum]

I tried setting up speed dial numbers following the tutorial on this page, but when I try to use it, I get "Not Acceptable." We've got Cisco SPA514g phones. Below is the server activity log for trying the speed dial and then manually dialing an outside line. I replaced the numbers with XxX, but they are correct.

29-Jan-2014 12:41:58.339	Leg L:1676.2[Line:10000>>XxXxXxX] is terminated: Cause: BYE from PBX
29-Jan-2014 12:41:58.338	[CM503008]: Call(C:1676): Call is terminated
29-Jan-2014 12:41:58.336	Leg L:1676.1[Extn] is terminated: Cause: BYE from 10.11.226.101:5060
29-Jan-2014 12:41:49.752	[CM503007]: Call(C:1676): Line:10000>>XxXxXxX has joined, contact <sip:[email protected]:5060>
29-Jan-2014 12:41:49.750	[CM503007]: Call(C:1676): Extn:1051 has joined, contact <sip:[email protected]:5060>
29-Jan-2014 12:41:49.748	L:1676.2[Line:10000>>XxXxXxX] has joined to L:1676.1[Extn]
29-Jan-2014 12:41:48.554	[CM503025]: Call(C:1676): Calling T:Line:10000>>XxXxXxX@[Dev:sip:[email protected]:5060] for L:1676.1[Extn]
29-Jan-2014 12:41:48.506	[CM503027]: Call(C:1676): From: Extn:1051 ("Tyler" <sip:[email protected]:5060>)  to  T:Line:10000>>XxXxXxX@[Dev:sip:[email protected]:5060]
29-Jan-2014 12:41:48.505	[CM503004]: Call(C:1676): Route 1: from L:1676.1[Extn] to T:Line:10000>>XxXxXxX@[Dev:sip:[email protected]:5060]
29-Jan-2014 12:41:48.505	Line limit check: Current # of calls for line Lc:10000(@Patton 4970[<sip:[email protected]:5060>]) is 0; limit is 23
29-Jan-2014 12:41:48.505	Call(C:1676): Call from Extn:1051 to XxXxXxX matches outbound rule 'Patton Outbound Rule 7 Digits'
29-Jan-2014 12:41:48.503	[CM503001]: Call(C:1676): Incoming call from Extn:1051 to <sip:[email protected]:5060>


29-Jan-2014 12:41:26.397	Leg L:1675.1[Extn] is terminated: Cause: BYE from PBX
29-Jan-2014 12:41:26.346	[CM503020]: Call(C:1675): Normal call termination. Call originator: Extn:1051. Reason: Terminated
29-Jan-2014 12:41:26.346	L:1675.1[Extn] failed to reach Line:10000>>XxXxXxXxXx, reason Not Acceptable HereReason Unknown
29-Jan-2014 12:41:26.345	Leg L:1675.2[Line:10000>>XxXxXxXxXx] is terminated: Cause: 406 Not Acceptable/INVITE from 10.11.226.253:5060
29-Jan-2014 12:41:26.345	Call to T:Line:10000>>XxXxXxXxXx@[Dev:sip:[email protected]:5060] from L:1675.1[Extn] failed, cause: Cause: 406 Not Acceptable/INVITE from 10.11.226.253:5060
29-Jan-2014 12:41:26.344	[CM503003]: Call(C:1675): Call to <sip:[email protected]:5060> has failed; Cause: 406 Not Acceptable/INVITE from 10.11.226.253:5060
29-Jan-2014 12:41:26.232	[CM503025]: Call(C:1675): Calling T:Line:10000>>XxXxXxXxXx@[Dev:sip:[email protected]:5060] for L:1675.1[Extn]
29-Jan-2014 12:41:26.183	[CM503027]: Call(C:1675): From: Extn:1051 ("Tyler" <sip:[email protected]:5060>)  to  T:Line:10000>>XxXxXxXxXx@[Dev:sip:[email protected]:5060]
29-Jan-2014 12:41:26.183	[CM503004]: Call(C:1675): Route 1: from L:1675.1[Extn] to T:Line:10000>>XxXxXxXxXx@[Dev:sip:[email protected]:5060]
29-Jan-2014 12:41:26.183	Line limit check: Current # of calls for line Lc:10000(@Patton 4970[<sip:[email protected]:5060>]) is 0; limit is 23
29-Jan-2014 12:41:26.183	Call(C:1675): Call from Extn:1051 to **04 matches outbound rule 'SD 04 L'
29-Jan-2014 12:41:26.181	[CM503001]: Call(C:1675): Incoming call from Extn:1051 to <sip:**[email protected]:5060>

Here is the outbound rule for our speed dial:

Here's the outbound rule for 10 digits:

 

[craigreilly]

I just tried it and worked for me on a Yealink.
I first tried a single asterick which did not work - but the double did.

We ended up using extensions for speed dials though -
All of our locations are 3 digit numbers. So we prepend with a 1.
So, 1xxx and the extension is set to forward to "mobile number" - but is actually the office number.

 

[TSlocum]

It's very strange because it works sometimes and not other times. We may end up doing 3 digits or something with just numbers since we use 4 for extensions.

 

[leejor]

Be sure that nothing (dial plan/special digits, etc) , within the set, is not misinterpreting the digits you are dialling.
There is no conflict with extension, or other internal numbers
That the rules are placed in the proper order, in the outbound rules, (they are read top to bottom).
That you are sending out the correct digits on the trunk.

I understand the security concerns, but with all dialled numbers X'd out, it's hard to determine what is actually happening.

 

[TSlocum]

We're just going to go with 3 digit numbers rather than **xx.

 

[complex1]

Hi,

Please setup the “Calls from Extension(s)” field with the range of extension from which the calls can come from.
e.g. 1000-1099

 

[TSlocum]

I think I found the problem. Even after changing it from **xx to 010, some would work and some wouldn't. I tried putting 0000-9999 in the "Calls from extensions" and also adding the extension groups without success. I then added a 1 in front of the number with an area code and it looks like it's working now.