Forwarding incoming call to Mobile number

Unanswered Question
Aug 11th, 2010
User Badges:

I am having this issue for a week already. I have tried to search on many resources but still cannot find out.
The   problem is customer want to forward incoming call to his Mobile  number.  I configured as follow and it was fail to forward incoming call  from  outside.
but I can forward to mobile if the incoming call is from internal extension. Any idea?


#ephone-dn  4  dual-line
number 563
pickup-group 1
call-forward busy xxxxxxxx
call-forward noan xxxxxxxx timeout 10


Would appreciate your help!

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 2.5 (4 ratings)
Loading.
paolo bevilacqua Wed, 08/11/2010 - 10:52
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Take "debug isdn q931" with "term mon" for the two cases.


Do not take other debugs. Do not use attachments.

paolo bevilacqua Thu, 08/12/2010 - 08:24
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Please report without using attachements as indicated before.

pyaykhaing789 Thu, 08/12/2010 - 09:05
User Badges:

Sorry man. Here it is..

Thanks!


debug isdn q931 & terminal mointor

Aug 12 13:33:51.400: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x0043
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Calling Party Number i = 0x4183, 'xxxx3124'
                Plan:ISDN, Type:Subscriber(local)
        Called Party Number i = 0xC1, 'xxxx0563'
                Plan:ISDN, Type:Subscriber(local)
Aug 12 13:33:51.404: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x8043 call
ID = 0x030B switch = primary-net5 interface = User
Aug 12 13:33:51.436: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x8
043
        Channel ID i = 0xA98381
                Exclusive, Channel 1
Aug 12 13:33:51.452: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8  callref = 0x80
43
        Progress Ind i = 0x8188 - In-band info or appropriate now available
Aug 12 13:34:01.472: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is
0x4 0x1, Calling num 9xxxx3124
Aug 12 13:34:01.472: ISDN Se0/0/0:15 Q931: Sending SETUP  callref = 0x02D3 callI
D = 0x8254 switch = primary-net5 interface = User
Aug 12 13:34:01.480: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x02D3
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA9839E
                Exclusive, Channel 30
        Calling Party Number i = 0x4183, '9xxxx3124'
                Plan:ISDN, Type:Subscriber(local)
        Called Party Number i = 0xC1, 'xxxx7249'
                Plan:ISDN, Type:Subscriber(local)
Aug 12 13:34:01.772: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x8
2D3
        Channel ID i = 0xA9839E
                Exclusive, Channel 30
Aug 12 13:34:02.156: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x
82D3
        Cause i = 0x829C - Invalid number format (incomplete number)
        Progress Ind i = 0x8288 - In-band info or appropriate now available
Aug 12 13:34:02.156: ISDN Se0/0/0:15 Q931: call_disc: PI received in disconnect;
Postpone sending RELEASE for callid 0x8254
Aug 12 13:34:02.164: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x
8043
        Cause i = 0x809C - Invalid number format (incomplete number)
        Progress Ind i = 0x8288 - In-band info or appropriate now available
Aug 12 13:34:02.244: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x004
3
        Cause i = 0x82E31E - Information element not implemented
Aug 12 13:34:02.248: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref =
0x8043
Aug 12 13:34:02.260: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8  callref = 0x02D
3
        Cause i = 0x82E31E - Information element not implemented
Aug 12 13:34:02.332: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref =
0x82D3

paolo bevilacqua Thu, 08/12/2010 - 10:10
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Try removing the leading 9 in calling number using voice translation-profile and rule.


Note, most likely you will not be able to display the original calling number. It will be overwritten by telco.

philip.e.denton Wed, 08/25/2010 - 07:56
User Badges:
  • Silver, 250 points or more

Why no attachments?


(n00b question I guess but I've seen this request multiple times)

Christopher Graham Wed, 08/11/2010 - 16:05
User Badges:
  • Cisco Employee,

Do you have anything configured under telephony-service for the call-forward pattern?  If not, try adding the following:


config t

telephony-service

call-forward pattern .T


See the doc below for more information:

http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucme/admin/configuration/guide/cmetrans.html#wp1056952


If this does not work, gather the following debugs:


debug voip ccapi inout

debug ephone detail mac


chris

pyaykhaing789 Thu, 08/12/2010 - 07:57
User Badges:

Hi Chris,

Thanks for your suggestion. I already configured call-forward pattern .T


Sincerely,

PK

asharsidd Thu, 08/12/2010 - 11:42
User Badges:

When the call is coming in - 1st call leg has calling party number without leading '9' while when it gets forwarded to mobile number I can see leading '9' in calling party number:


Aug 12 13:33:51.400: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x0043
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Calling Party Number i = 0x4183, 'xxxx3124'
                Plan:ISDN, Type:Subscriber(local)
        Called Party Number i = 0xC1, 'xxxx0563'
                Plan:ISDN, Type:Subscriber(local)

.

.

.

.

        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA9839E
                Exclusive, Channel 30
        Calling Party Number i = 0x4183, '9xxxx3124'
                Plan:ISDN, Type:Subscriber(local)
        Called Party Number i = 0xC1, 'xxxx7249'
                Plan:ISDN, Type:Subscriber(local)
Aug 12 13:34:01.772: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x8
2D3
        Channel ID i = 0xA9839E
                Exclusive, Channel 30
Aug 12 13:34:02.156: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x
82D3
        Cause i = 0x829C - Invalid number format (incomplete number)



Invalid format indicates that may be its not matching a proper dialpeer or your dialpeer is stripping digits. Verify whether the format of the number is correct as destination telco is rejecting call.

paolo bevilacqua Thu, 08/12/2010 - 12:36
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

When the call is coming in - 1st call leg has calling party number  without leading '9' while when it gets forwarded to mobile number I can  see leading '9' in calling party number:


That is because there is a rule to prefix 9 to calling number, normally done when an external access digits is used.

Note in many countries it is possible to avoid using an access digit altogether, with many advantages.


Invalid format indicates that may be its not matching a proper dialpeer or your dialpeer is stripping digits. Verify whether the format of the number is correct as destination telco is rejecting call.


Incorrect, DP is mached and digit stripping is correct. Whta happens, telco may not like the number format, and type / plan. These are easy to fix anyway.

pyaykhaing789 Wed, 08/18/2010 - 20:55
User Badges:

So, do I need to remove"9" from voice translation-rule? Here's my voice translation-rule.

Thanks.


voice translation-rule 1
rule 1 /ab810710/ /ab800690/
!
voice translation-rule 2
rule 1 /^/ /9/
!
!
voice translation-profile PSTN-IN
translate calling 2
translate called 1

paolo bevilacqua Thu, 08/19/2010 - 01:22
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

You are currently adding in when the calls come in.

You need to remove 9 when the call goes out.


For that you need two separate translation-profiles and rules.

pyaykhaing789 Wed, 08/25/2010 - 04:50
User Badges:

I changed translation profiles and rules as follow,

voice translation-rule 1
rule 1 /ab810719/ /ab800590/
!
voice translation-rule 2
rule 1 /^/ //
!
!
voice translation-profile PSTN-IN
translate called 1
!
voice translation-profile PSTN-OUT
translate calling 2

But still cannot forward to my mobile. fyi, I haven't conifigured Voice mail and AA. Does it make sense?

Thanks for your kind support.

Regards,

PK

debug isdn q931 & terminal mointor

CME#
Aug 25 10:35:44.232: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x0054
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Calling Party Number i = 0x4183, 'abc98885'
                Plan:ISDN, Type:Subscriber(local)
        Called Party Number i = 0xC1, 'abc00563'
                Plan:ISDN, Type:Subscriber(local)
Aug 25 10:35:44.232: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x8054 callID = 0x0719 switch = primary-net5 interface = User
Aug 25 10:35:44.268: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x8054
        Channel ID i = 0xA98381
                Exclusive, Channel 1
Aug 25 10:35:44.276: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8  callref = 0x8054
        Progress Ind i = 0x8188 - In-band info or appropriate now available
Aug 25 10:35:59.296: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x4 0x1, Calling num 96898885
Aug 25 10:35:59.296: ISDN Se0/0/0:15 Q931: Sending SETUP  callref = 0x05BD callID = 0x853E switch = primary-net5 interface = User
Aug 25 10:35:59.296: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x05BD
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA9839E
                Exclusive, Channel 30
        Calling Party Number i = 0x4183, 'abc98885'
                Plan:ISDN, Type:Subscriber(local)
        Called Party Number i = 0xC1, 'abc87249'
                Plan:ISDN, Type:Subscriber(local)
Aug 25 10:35:59.600: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x85BD
        Channel ID i = 0xA9839E
                Exclusive, Channel 30
Aug 25 10:35:59.972: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x85BD
        Cause i = 0x829C - Invalid number format (incomplete number)
        Progress Ind i = 0x8288 - In-band info or appropriate now available
Aug 25 10:35:59.976: ISDN Se0/0/0:15 Q931: call_disc: PI received in disconnect; Postpone sending RELEASE for callid 0x853E
Aug 25 10:35:59.980: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x8054
        Cause i = 0x809C - Invalid number format (incomplete number)
        Progress Ind i = 0x8288 - In-band info or appropriate now available
Aug 25 10:36:00.064: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x0054
        Cause i = 0x82E31E - Information element not implemented
Aug 25 10:36:00.064: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8054
Aug 25 10:36:00.080: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8  callref = 0x05BD
        Cause i = 0x82E31E - Information element not implemented
Aug 25 10:36:00.152: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x85BD
CME#

paolo bevilacqua Wed, 08/25/2010 - 04:57
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Add this under serial interface:


isdn map address . type unknown plan unknown

pyaykhaing789 Wed, 08/25/2010 - 08:46
User Badges:

I've tried this command under serial interface but unluckily still cannot forward to my mobile.

#isdn map add type plan unknown type unknown

Thanks all of your support.


Regards,

PK

paolo bevilacqua Wed, 08/25/2010 - 09:54
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Please take the same debug for a normal, working calld. And the call forwardin debug again, to compare.

Actions

This Discussion

Related Content