VOIP on 5350 and a bug or ....

[rsahafi]

I have seen a problem that I still can not find any solution for it . It is under 5350 ONLY.

When we have two carrier and carrier number one could not terminate the call by any reason and Carrier number two terminate the call, after the call has been finished, I have two START/STOP signal from the router side with the same Prefix of Carrier number 1. I am sure that call is terminating on carrier number two, but the STOP signal shows that call terminated at carrier number ONE. It seems that information for START/STOP will repeated for carrier number two. Any one have any idea.

in below example, call can not terminate at dial-peer 111, and will go to dial-peer 222 and will terminate. but the STOP signal shows the destination number as 11101144...... instead of 22201144....

even the h323-remote-address=198.198.104.1

is correct , I mean it shows the second carrier ip address, but the destination number ( Called-Station-Id ) is not correct.

I have tested this thing, on 3 different 5350 and different IOS, 12.2 and 12.3 . Result is the same. But the same config undser 5300 working well !!!

any one can help me?

here is the relative config,

aaa authentication login h323 group radius

aaa authentication login telnet local

aaa authentication login voip group radius

aaa authorization exec h323 group radius

aaa authorization exec telnet if-authenticated

aaa accounting send stop-record authentication failure

aaa accounting exec default start-stop group radius

aaa accounting connection default start-stop group radius

aaa accounting connection h323 start-stop group radius

aaa accounting connection voip start-stop group radius

gw-accounting aaa

acct-template callhistory-detail

radius-server host 192.168.1.20 auth-port 1845 acct-port 1846

radius-server retransmit 1

radius-server key xxxxxxxxxxxxxx

radius-server authorization permit missing Service-Type

radius-server vsa send accounting

radius-server vsa send authentication

translation-rule 111

Rule 0 ^01144 11144

dial-peer voice 111 voip

preference 1

destination-pattern 01144T

translate-outgoing called 111

session target ipv4:200.200.102.2

dtmf-relay h245-signal h245-alphanumeric

translation-rule 222

Rule 0 ^01144 22244

dial-peer voice 222 voip

preference 2

destination-pattern 01144T

translate-outgoing called 222

session target ipv4:198.198.104.1

dtmf-relay h245-signal h245-alphanumeric

[irisrios]

This seems like a bug. I remember seeing a similar known bug on BugToolKit regarding the duplicate Start/Stop records.

[rsahafi]

Dear Irisrios,

Do you have any suggestion? how can I find a solution for it?

[lucix]

Hi,

I am facing the same problem right now. The answer is "RADIUS Packet Suppression for VoIP Gateway Rotary Dial Peer Attempts" (you can find the description if you search it on the cisco site).

However, you will need cisco IOS greater than 12.2(11)T.

My problem is that in versions prior to 12.2(11)T, when the gateway issued a radius authentication request, the packet had the source port 1645, but in the newer IOS releases (including 12.3) the port varies (it starts by sending auth requests with the sport 21645 but after a while it sends requests with the sport 21646). I would like to know if you or anyone at cisco or who reads this can tell me how to make my 5350 to send a packet to the radius server with sport 1645 (or any sport but not varying).

Thank you, And I hope this solves your problem.

Lucix