outgoing isdn mobile calls failing

Unanswered Question

I seem to have a problem with the config on my uc520 that I need help with. I am unable to make consecutive calls to mobile numbers (10 digits long) going out through an isdn connection. I seem to be able to call any landline numbers (8 digits long) so it only affects the mobile numbers. At first I thought it was a translation problem, but what confuses me is that it does not affect every call (to the same number).

My setup is as follows. I have a 10 line E1 that I have connected.

card type e1 0 2

network-clock-select 1 E1 0/2/0

controller E1 0/2/0

pri-group timeslots 1-10,16

I have setup a translation rule to remove the leading 0 from outgoing calls as follows:

voice translation-rule 1116

rule 1 /^0/ //

i have enabled debugs 'voip translation' and 'isdn events' and tested the calls. When the call is successful the following debug can be seen
.Oct 16 05:33:09.712: //-1/393C53B68A0F/RXRULE/sed_subst: Successful substitution; pattern=00412345678 matchPattern=^0 replacePattern= replaced pattern=0412345678
.Oct 16 05:33:09.716: //-1/393C53B68A0F/RXRULE/regxrule_tg_translate: calling_number=81234567 calling_octet=0x0
        called_number=0412345678 called_octet=0x80
        redirect_number= redirect_type=0 redirect_plan=0
.Oct 16 05:33:09.716: //-1/393C53B68A0F/RXRULE/regxrule_stack_push_RegXruleNumInfo_internal: Success in ccTDUtilSetDataInstance
.Oct 16 05:33:09.720: ISDN Se0/2/0:15 EVENT: process_pri_call: call id 0x9A5E, number 0412345678, Guid 393C53B68A0F, speed 0, call type VOICE, redial No, CSM call No, pdata Yes
.Oct 16 05:33:09.792: ISDN Se0/2/0:15 EVENT: process_rxstate: ces/callid 1/0x9A5E calltype 2 CALL_PROCEEDING
When the call fails, the following debug can be seen:
.Oct 16 05:33:22.780: //-1/410703B58A14/RXRULE/sed_subst: Successful substitution; pattern=00412345678 matchPattern=^0 replacePattern= replaced pattern=0412345678
.Oct 16 05:33:22.780: //-1/410703B58A14/RXRULE/regxrule_tg_translate: calling_number=81234567 calling_octet=0x0
        called_number=0412345678 called_octet=0x80
        redirect_number= redirect_type=0 redirect_plan=0
.Oct 16 05:33:22.780: //-1/410703B58A14/RXRULE/regxrule_stack_push_RegXruleNumInfo_internal: Success in ccTDUtilSetDataInstance
.Oct 16 05:33:22.788: ISDN Se0/2/0:15 EVENT: process_pri_call: call id 0x9A5F, number 412345678, Guid 410703B58A14, speed 0, call type VOICE, redial No, CSM call No, pdata Yes
.Oct 16 05:33:22.856: ISDN Se0/2/0:15 EVENT: process_rxstate: ces/callid 1/0x9A5F calltype 2 CALL_PROCEEDING
What I can see is that another leading 0 seems to be removed after the translation rule has been actioned. There is only about 10 seconds between attempts being made, so I am unsure why the cisco is treating the 2 calls differently. I'm not sure what this means, or if there is any other debugs that can shed more light on this.
Hope you can help
Stephen
I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
David Harper Thu, 10/15/2009 - 22:54

Hi Stephen,

Can you either attach your config with passwords and other private data removed, or else email it to me directly.  Also, would it be possible to get debugs from a failed call?  A 'debug voice ccapi inout' should be a good start.

Cheers,

Dave.

David Harper Thu, 10/15/2009 - 23:49

Just to close the loop with the rest of the community, it seems that there are in fact two matching dial-peers for mobile calls with slightly different configurations.  The upshot of this is that calls through one peer would succeed and through the other would fail.  Removing the incorrectly configured peer should fix the problem.

Cheers,

Dave.

Actions

This Discussion