"The extension number is invalid" forward to mobile phone

Unanswered Question
May 4th, 2008
User Badges:

Hi, We have CME 4.1. All of the users have both inside desk extensions in a 300 range, and mobile phones in a 500 extension range, with the exception of two DN's set up for mobile phones only.


The two DN's for mobile phones have call-forward all to the mobile number, prefaced by the digit "9".


When calling in on the main line, and entering extension 518, or 522, I get the message "The extension is invalid".


Here are Sample DN's to illustrate:


This dn for a mobile works, user also has desk extension matching mobile extension with only first digit changed:

ephone-dn 45 dual-line

number 515

label Bruce, James (Mobile)

description Bruce, James (Mobile)

name Bruce, James (Mobile)

call-forward all 9xxxxxxx (number obscured)

ephone-dn 17 dual-line

number 315

label Bruce, James (315)

description VNS

name Bruce, James

call-forward busy 400

call-forward noan 400 timeout 10

hold-alert 30 originator


This is one of the ones that do not work:

(user has no 3xx extension)

ephone-dn 25

number 522

label Acosta, Gerardo (Mobile)

description Acosta, Gerardo (Mobile)

name Acosta, Gerardo (Mobile)

call-forward all 99941544

hold-alert 30 originator

When dialing in and entering 522 for the extension from the AA, We get "The extension is invalid"


Any body have any answers for this? Like I said, every other mobile extension with a 5xx extension works fine.

I tried researhing this, and I get pointers to the AA script, but can't see anywhere in that any problem.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Rob Huffman Sun, 05/04/2008 - 15:00
User Badges:
  • Super Red, 40000 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi James,


Maybe you are running into this CUE default, that allows transfers to Internal (associated to CUE Mailbox) users only. Have a look;


Internal and External Destinations


Up to Cisco Unity Express 2.0, the system AA allowed for the transfer calls to any destination,it treated the destination merely as a string of digits, and any call dialable on the associated call agent would succeed. To limit the destinations to which the AA can transfer calls (such as no calls to the PSTN), the call agent's features,such as Class of Restriction (COR) on Cisco CME were required.


**As of Cisco Unity Express Release 2.1, the system AA has a parameter to control whether calls are allowed to transfer only to internal numbers (default operation), or to internal and external numbers. Your own custom AA scripts can employ similar mechanisms to limit the valid destinations of calls.*** The system AA script parameter is (the value of the allowExternalTransfers parameter).


An internal number is considered to be an extension that exists in Cisco Unity Express's LDAP directory. Information that appears in LDAP includes all extensions defined and associated with a user (Configure > Users) on Cisco Unity Express. This does not include remote user (Configure > Remote Users) definitions entered on Cisco Unity Express for networking spoken name confirmation (these are not stored in LDAP). The validity of a destination number is independent of extension length or dialing plans and is not coordinated with your call agent's dial plan on what might be local extensions versus remote extensions.


Cisco Unity Express considers an extension that appears in an LDAP entry an internal destination. External destinations include everything else, such as the following:


All other extensions that exist at the local site, but do not appear in the Cisco Unity Express configuration, such as local phones/extensions that do not have mailboxes.


All VoIP destinations, such as extensions present at other sites, but a PSTN call is not required to reach them.


All PSTN destinations.


If you want to refine the destinations that the Cisco Unity Express AA can transfer calls to, you have to limit calls either on the call agent (with features such as COR), or write a custom Cisco Unity Express AA script that does the checking based on your requirements (such as perhaps extension length, or numbers starting with certain sequences such as 9).


From this good AA Design doc;


http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_implementation_design_guide_chapter09186a00804993c2.html#wp1011696


Hope this helps!

Rob



jamesbruce Sun, 05/04/2008 - 15:58
User Badges:

Thanks Rob, I will check that out. It is just strange that calls transferred from AA to other mobile extensions(5xxx)work...

anyway, I'll take a look, thanks.

jamesbruce Sun, 05/04/2008 - 17:33
User Badges:

Hi Rob,

I did a show call history voice after calling in, getting the AA, and dialing ext 518(extension invalid) and ext 515(known good mobile extension) and this is the out put from the call history. It looks like the translated redirect fails on 518:


Call to ext 518

GENERIC:

SetupTime=-1260209376 ms

Index=26158

PeerAddress=9xxxxxxx(# omitted)

PeerSubAddress=

PeerId=752

PeerIfIndex=40

LogicalIfIndex=22

DisconnectCause=10

DisconnectText=normal call clearing (16)

ConnectTime=-1260209296 ms

DisconnectTime=-1260184276 ms

CallDuration=00:00:25 sec

CallOrigin=2

ReleaseSource=1

ChargedUnits=0

InfoType=speech

TransmitPackets=492

TransmitBytes=82020

ReceivePackets=573

ReceiveBytes=91680

TELE:

ConnectionId=[0xEDBFE715 0x197611DD 0x983F9DBF 0x3E9523F9]

IncomingConnectionId=[0xEDBFE715 0x197611DD 0x983F9DBF 0x3E9523F9]

CallID=29951

TxDuration=11135 ms

VoiceTxDuration=11135 ms

FaxTxDuration=0 ms

CoderTypeRate=None

NoiseLevel=-71

ACOMLevel=18

SessionTarget=

ImgPages=0

CallerName=WIRELESS CALLER

CallerIDBlocked=False

LongDurationCallDetected=no

LongDurCallTimeStamp=

LongDurCallDuration=

OriginalCallingNumber=559xxxxxxx(number omitted)

OriginalCallingOctet=0x0

OriginalCalledNumber=

OriginalCalledOctet=0x80

OriginalRedirectCalledNumber=

OriginalRedirectCalledOctet=0x0

TranslatedCallingNumber=9246xxxx(#omitted)

TranslatedCallingOctet=0x0

TranslatedCalledNumber=401

TranslatedCalledOctet=0x80

TranslatedRedirectCalledNumber=

TranslatedRedirectCalledOctet=0x0

GwReceivedCallingNumber=559xxxxxxx(#omitted)

GwReceivedCallingOctet3=0x0

GwReceivedCallingOctet3a=0x0

DSPIdentifier=0/2:1


Call to ext 515 (known good Mobile ext, works)

GENERIC:

SetupTime=-1260196916 ms

Index=26159

PeerAddress=9xxxxxxx(# omitted)

PeerSubAddress=

PeerId=758

PeerIfIndex=46

LogicalIfIndex=24

DisconnectCause=10

DisconnectText=normal call clearing (16)

ConnectTime=-1260194166 ms

DisconnectTime=-1260184266 ms

CallDuration=00:00:09 sec

CallOrigin=1

ReleaseSource=1

ChargedUnits=0

InfoType=speech

TransmitPackets=0

TransmitBytes=0

ReceivePackets=0

ReceiveBytes=0

TELE:

ConnectionId=[0xF52C8643 0x197611DD 0x98459DBF 0x3E9523F9]

IncomingConnectionId=[0xEDBFE715 0x197611DD 0x983F9DBF 0x3E9523F9]

CallID=29954

TxDuration=0 ms

VoiceTxDuration=0 ms

FaxTxDuration=0 ms

CoderTypeRate=None

NoiseLevel=0

ACOMLevel=0

SessionTarget=

ImgPages=0

CallerName=WIRELESS CALLER

CallerIDBlocked=False

LongDurationCallDetected=no

LongDurCallTimeStamp=

LongDurCallDuration=

OriginalCallingNumber=9xxxxxxx(# omitted)

OriginalCallingOctet=0x0

OriginalCalledNumber=401

OriginalCalledOctet=0x80

OriginalRedirectCalledNumber=

OriginalRedirectCalledOctet=0x0

TranslatedCallingNumber=9xxxxxxx(# omitted)

TranslatedCallingOctet=0x0

TranslatedCalledNumber=9xxxxxxx(# omitted)

TranslatedCalledOctet=0x80

TranslatedRedirectCalledNumber=515

TranslatedRedirectCalledOctet=0x0

GwOutpulsedCalledNumber=9xxxxxxx(# omitted)

GwOutpulsedCalledOctet3=0x80

GwReceivedCallingNumber=559xxxxxxx(# omitted)

GwReceivedCallingOctet3=0x0

GwReceivedCallingOctet3a=0x0

GwOutpulsedCallingNumber=9xxxxxxx(# omitted)

GwOutpulsedCallingOctet3=0x0

GwOutpulsedCallingOctet3a=0x0

GwOutpulsedRedirectNumber=515

GwOutpulsedRedirectOctet3=0x0

GwOutpulsedRedirectOctet3a=0x80

DSPIdentifier=0/2:2

rtr_2821#



Any Ideas, or do you still think it is the AA?

Rob Huffman Sun, 05/04/2008 - 18:40
User Badges:
  • Super Red, 40000 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi James,


I do still think this is the AA;


An internal number is considered to be an extension that exists in Cisco Unity Express's LDAP directory. Information that appears in LDAP includes all extensions defined and associated with a user (Configure > Users) on Cisco Unity Express. This does not include remote user (Configure > Remote Users) definitions entered on Cisco Unity Express for networking spoken name confirmation (these are not stored in LDAP). The validity of a destination number is independent of extension length or dialing plans and is not coordinated with your call agent's dial plan on what might be local extensions versus remote extensions.


Cisco Unity Express considers an extension that appears in an LDAP entry an internal destination. External destinations include everything else, such as the following:


All other extensions that exist at the local site, but do not appear in the Cisco Unity Express configuration, such as local phones/extensions that do not have mailboxes.


Rob

Actions

This Discussion