cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
521
Views
3
Helpful
3
Replies

Strange Call process such as "Ping-Pong" between gateway and PBX.

johnyoon75
Level 1
Level 1

Hello.

I have a strange thing in our voip network.

Sometimes, some strange call(i think this call maded by someone using wrong number) occured in our network. At this time, i tried to see the status of the call using show voice call status, most of channels used by strange call.

Here is the capture.

gateway#sh voice call status

CallID CID ccVdb Port DSP/Ch Called # Codec Dial-peers

0x16421 6C2 0x4591B75C 1/1:15.3 1/1 *1101180 g711ulaw 25/2

0x16430 1A49 0x454ECDDC 1/0:15.14 4/3 75435779 g711ulaw 1/200

0x16436 1A4C 0x454ECDDC 1/0:15.15 2/2 963474703 g711ulaw 1/203

0x1647C 1A5E 0x454ECDDC 1/0:15.21 2/6 75434063 g711ulaw 1/200

0x1648F 6D9 0x454ECDDC 1/0:15.8 4/4 *822795431 g711ulaw 25/1

0x16496 1A65 0x454ECDDC 1/0:15.20 3/2 75431357 g711ulaw 1/200

0x1655B 6F0 0x454ECDDC 1/0:15.1 3/3 *1107938 g711ulaw 25/1

0x16566 1AA9 0x454ECDDC 1/0:15.13 1/2 97223399 g711ulaw 1/203

0x1656C 1AAB 0x454ECDDC 1/0:15.22 2/1 75430439 g711ulaw 1/200

0x1656F 6F5 0x454ECDDC 1/0:15.5 3/4 *1101068 g711ulaw 25/1

0x16570 1AAC 0x454ECDDC 1/0:15.18 2/3 75435453 g711ulaw 1/200

0x16573 6F6 0x454ECDDC 1/0:15.3 1/4 *1101655 g711ulaw 25/1

0x16578 1AAF 0x454ECDDC 1/0:15.28 4/1 7608562 None 1/2

0x16579 1AAF 0x4591B75C 1/1:15.2 4/2 *7608562 None 2/1

0x1657A 1AB0 0x454ECDDC 1/0:15.9 4/5 7608562 None 1/2

0x1657B 1AB0 0x4591B75C 1/1:15.5 4/6 *7608562 None 2/1

0x1657C 1AB1 0x454ECDDC 1/0:15.7 1/7 7608562 None 1/2

0x1657D 1AB1 0x4591B75C 1/1:15.6 2/5 *7608562 None 2/1

0x1657E 1AB2 0x454ECDDC 1/0:15.25 2/8 7608562 None 1/2

0x1657F 1AB2 0x4591B75C 1/1:15.7 2/9 *7608562 None 2/1

0x16580 1AB3 0x454ECDDC 1/0:15.19 3/7 7608562 None 1/1

0x16581 1AB3 0x454ECDDC 1/0:15.10 4/7 *7608562 None 1/1

0x16582 1AB4 0x454ECDDC 1/0:15.24 3/8 7608562 None 1/1

0x16583 1AB4 0x454ECDDC 1/0:15.11 1/8 *7608562 None 1/1

0x16584 1AB5 0x454ECDDC 1/0:15.17 2/10 7608562 None 1/1

0x16585 1AB5 0x454ECDDC 1/0:15.26 3/9 *7608562 None 1/1

0x16586 1AB6 0x4591B75C 1/1:15.20 4/8 7608562 None 1/2

0x16587 1AB6 0x4591B75C 1/1:15.8 4/9 *7608562 None 2/1

0x16588 1AB7 0x4591B75C 1/1:15.9 1/9 7608562 None 1/2

0x1658A 1AB7 0x4591B75C 1/1:15.10 1/10 *7608562 None 2/1

0x1658B 1AB8 0x4591B75C 1/1:15.23 2/7 7608562 None 1/2

0x1658C 1AB8 0x4591B75C 1/1:15.11 4/10 *7608562 None 2/1

0x1658D 1AB9 0x4591B75C 1/1:15.22 3/10 7608562 None 1/2

0x165AE 1AB9 0x4591B75C 1/1:15.4 3/5 *7608562 None 2/1

0x165A2 1AC1 0x4591B75C 1/1:15.21 1/12 7907846 g711ulaw 1/201

0x165AF 1AC5 0x4591B75C 1/1:15.17 2/4 7608562 None 1/2

0x165B0 1AC5 0x4591B75C 1/1:15.12 3/11 *7608562 None 2/1

0x165B1 1AC6 0x4591B75C 1/1:15.15 2/11 7608562 None 1/2

0x165B2 1AC6 0x4591B75C 1/1:15.13 1/11 *7608562 None 2/1

0x165B3 1AC7 0x4591B75C 1/1:15.14 4/11 7608562 None 1/2

0x165B4 1AC7 0x4591B75C 1/1:15.18 2/12 *7608562 None 2/1

0x165B5 1AC8 0x454ECDDC 1/0:15.2 3/12 7608562 None 1/2

0x165B6 1AC8 0x4591B75C 1/1:15.19 4/12 *7608562 None 2/1

0x165B7 1AC9 0x454ECDDC 1/0:15.12 1/13 7608562 None 1/1

0x165B9 1AC9 0x454ECDDC 1/0:15.29 2/13 *7608562 None 1/1

29 active calls found

Just One call exhausted up to 35 channels on two E1.

I think this call made someone who was tried to make a call with wrong number.

Anyone have the same or similar experience just to me?

Regards,

john

3 Replies 3

dleblanc
Level 1
Level 1

Are you by any chance using H.323? This problem can happen if the called device (IP phone) is unreachable, and the "huntstop" command is not placed on the last VoIP peer you want searched, it will keep going and more than likely will find the wild card that's set to send calls to the PSTN. This is how the snowball starts and won't stop until all channels are used up. It will also happen if the called party on a remote H323 VGW is busy and you don't have huntstops on the POTS peers on that side. THe call will get kicked back to CCM and will start all over.

Hello.

You means, If i configure "huntstop" under all of dial-peer, I can avoid the call loop anymore?

Alternatively you could use CoR (class of restriction) to deny the ability to reach dial-peers that point to the PBX from dial-peers that match inbound calls from the PBX.

This would prevent the loop.... this doc outlines CoR config if you're not familiar with it...

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a008019d649.shtml

Regards

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!