• Advertisement

CME Call forward All Issue

Cisco CallManager, Cisco CallManager Express and IP Video

Re:CME Call forward All Issue

Postby Guest » Sun Mar 19, 2006 1:27 am


Ok, the router is copying plan/type for outgoing as received on incoming. But, type "subscriber" is not accepted.

Try making your voice translation-rule 30 as:

rule 1 /^1(73[4-9][0-9])/ /63051/ type any unknown

rule 2 /.*/ /63057373/ type any unknown

I also think you do not need the three "voice"commands above mentioned, but that's another issue.

Let us know if it works and do not forget to rate useful posts!

Guest
 

Advertisement

Re:CME Call forward All Issue

Postby Guest » Sun Mar 19, 2006 2:03 am


hi, thanks for your advise, but still no luck.. I've removed the 3 configurations as you have pointed as well as amended the translation pattern..oh yeah after removing the 3 lines, instead of getting a ringing tone, this time it is just a Telco engage tone. my debug of isdn q931 still shows similar results:

132637: Jun 15 22:44:26.488 SGT: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callr

ef = 0x0048

        Sending Complete

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA9839D

                Exclusive, Channel 29

        Calling Party Number i = 0x4183, '90298053'

                Plan:ISDN, Type:Subscriber(local)

        Called Party Number i = 0xC1, '63057340'

                Plan:ISDN, Type:Subscriber(local)

        High Layer Compat i = 0x9181

132638: Jun 15 22:44:26.500 SGT: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x8048

        Channel ID i = 0xA9839D

                Exclusive, Channel 29

132639: Jun 15 22:44:26.508 SGT: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Calling num 63057373

132640: Jun 15 22:44:26.508 SGT: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x4 0x1, Called num 90298053

132641: Jun 15 22:44:26.508 SGT: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x0A08

        Sending Complete

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA9839F

                Exclusive, Channel 31

        Calling Party Number i = 0x0183, '63057373'

                Plan:ISDN, Type:Unknown

        Called Party Number i = 0xC1, '90298053'

                Plan:ISDN, Type:Subscriber(local)

        High Layer Compat i = 0x9181

132642: Jun 15 22:44:26.840 SGT: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x8A08

        Channel ID i = 0xA9839F

                Exclusive, Channel 31

132643: Jun 15 22:44:27.244 SGT: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x8A08

        Cause i = 0x829C - Invalid number format (incomplete number)

        Progress Ind i = 0x8288 - In-band info or appropriate now available

132644: Jun 15 22:44:27.244 SGT: ISDN Se0/0/0:15 Q931: call_disc: PI received in

disconnect; Postpone sending RELEASE for callid 0x8989

132645: Jun 15 22:44:27.272 SGT: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x8048

        Cause i = 0x829C - Invalid number format (incomplete number)

        Progress Ind i = 0x8288 - In-band info or appropriate now available

132646: Jun 15 22:44:27.412 SGT: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x0048

        Cause i = 0x82E31E - Information element not implemented

132647: Jun 15 22:44:27.412 SGT: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8048

132648: Jun 15 22:44:27.420 SGT: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8  callref = 0x0A08

132649: Jun 15 22:44:27.512 SGT: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x8A08

Guest
 

Re:CME Call forward All Issue

Postby Guest » Sun Mar 19, 2006 2:42 am


Alvin,

my bad. I had you modify the calling number plan/type, but left the called number plan/type (that is even more important), unchanged.

You can do that in three ways, pick the one you like better:

- under interface e0/0/0:15, "isdn map address ... type unknown"

or, under the outgoing DP, "numbering-type unknown"

or, a translation-rule outgoing for called, matching everything like: // // type any unknown. You can apply it either at DP or voice-port level.

Let us know if it works!

 

Guest
 

Re:CME Call forward All Issue

Postby Guest » Sun Mar 19, 2006 3:19 am


It's working! The help is greatly appreciated! am I right to assume that when you set the numbering-type to any unknown, you are in fact specifying a wildcard to match any type of offered and presented numbering-type?

Also, here's what is another task for me relating to this. I've removed the 2nd rule of the voice translation hoping that when handphone A calls the DID of IP Phone, as it redirects to another Handphone B, handphone B will be able to see the calling number as the call-forwarding IP Phone DID. I do think my Telco prevents the CME from forwarding the original calling number of Handphone A to be shown in Handphone B. That's why i'm seeing the trunk number as the calling number. Any fantastic ways to send the caller-id of the IP Phone to the forwarded number?

Guest
 

Re:CME Call forward All Issue

Postby Guest » Sun Mar 19, 2006 4:43 am


Glad to know it worked. The "numbering-type" under DP will simply set the desired type for all and any call going out that DP.

Now for your other question, you are correct that is not possible to present the original calling number, because it does not belong to the numbers assigned to you by telco.

And yes, there is a fantastic way to send instead the DID of the ephone-DN on which the call-forwarding has been set. This uses the little-know loopback-dn feature. See:

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Unified%20Communications%20and%20Video&topic=IP%20Telephony&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1dde396e/11#selected_message

Beside the solution that I gave, you will find some more in-depth discussion with Marco Pizzi that is another CME hardcore adept.

Thanks for the nice rating and good luck!

Guest
 

PreviousNext


  • Advertisement


Similar topics


Return to Cisco IP Communications

Who is online

Users browsing this forum: Google [Bot] and 2 guests