Thanks @Rob.

But I have a confusion, this is not a IP to IP call (like the concept we have for CUBE), here both of the ingress and outgress calls are over PRI i.e. over TDM channel, do we really need this 'allow-connection' command for this case?

Thanks again!

Hi All,

Thanks for all your reply, I am getting an assertion failure message when i try to hairpin calls.

I can see calls coming in to the gateway by matching incoming dial-peer and then the called number gets translated and matches the outbound dial-peer but the calls are not going out of PRI. I am getting an assertion failure message after matching the outbound pots dial-peer..

Please suggest.

Thanks,

It's my honor to having both of you here, +5 for you too sir for both of your continuous contributions.

@aravindhanelango: please post your running-config, 'sh isdn status' and 'debug isdn q931' while failing the call.

Hi All,

I was able to simulate the hairpinning with different gateway running same IOS and with same configuration.

It seems i was hitting a bug with that gateway.

Thanks for all your help..

Please find the config which i used...

voice translation-rule 1
rule 1 /4734490/ /94544653/
!
!
voice translation-profile test
translate called 1

controller E1 0/1/0
framing NO-CRC4
pri-group timeslots 1-31
description >>> PRI E10 <<<<

interface Serial0/1/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
no cdp enable

dial-peer voice 100 pots
translation-profile incoming test
incoming called-number 4734490
direct-inward-dial
port 0/1/0:15
!
dial-peer voice 200 pots
destination-pattern 94544653
  port 0/1/0:15
forward-digits 7

I have also attached the Q931 debug for a successful call.

So you got your answer, it's the IOS.

Try to get next/previous release of your IOS, please read the known issues first before downloading it from CCO.