No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

One-way call issue due to wrong next hop in AR2200

Publication Date:  2019-07-17  |   Views:  308  |   Downloads:  0  |   Author:  SU1001784671  |   Document ID:  EKB1000049411


Issue Description

A customer configured an AR to connect to IMS network using SIP AT0 trunk. After he finished the configuration, the SIP AT0 trunk can register to IMS network, and he can make the outgoing call incoming call, but there was a one-way call issue. He can hear the voice from other end, but the other end can’t hear his voice.
This is the topology:

In the topology, if the customer called from the phone 901455 connecting to AR to the remote phone 232505, he can hear the voice from other end, but the other end can’t hear his voice. If the customer replaced AR with an IP Phone, then this IP Phone will get the number 901454 and the IP address, then the call works right, no one-way call issue.

The related voice configuration in AR2200:
voip-address media interface GigabitEthernet 0/0/0.30
voip-address signalling interface GigabitEthernet 0/0/0.30
area-code xx 901
pbx default-country-code xx default-area-code 901
trunk-group sip sip trunk-circuit
  signalling-address ip port 5060
  peer-address static 5060 //The address of SBC in IMS network
callprefix 2
  enterprise default centrex hw_centrex
  prefix 2
  call-type category basic-service attribute 3
  digit-length 1 20
  destination-location inter-office
  callroute trunkgroup1 sip
callprefix 0901
  prefix 0901
  call-type category basic-service attribute 1
  digit-length 4 20
pbxuser 455 pots   // the local number
  port 2/0/3
  telno 455
  call-right in international-toll out international-toll
  centrex hw_centrex 455
  service-right call disable

Alarm Information


Handling Process

(1) Checked the configuration of AR, since the outgoing call started working, so the outgoing call configuration is OK.
(2) If the customer replaced AR with an IP Phone, then the call works right, no one-way call issue. packet and found that the peer address was, which is same as that configured on AR.
(3) packet in the outgoing call, we can see that the AR had sent the voice from local, but we didn’t know why the other end couldn’t hear it.

(4) So we asked the customer packet from IP Phone side. From the result we can find that AR didn’t send voice traffic to IP Phone. Compare to step(3), it seems that it’s IMS network problem, it dropped the voice traffic sent from AR( to IP Phone( .

(5) We asked the customer to ping from AR( to IP Phone( to test if the route is reachable, and it turned out that the route is not reachable.
   Check the configuration again, we found there were two static routes.
interface GigabitEthernet0/0/0.20
description Mgmt
dot1q termination vid 20
ip address
interface GigabitEthernet0/0/0.30
description VPN
dot1q termination vid 30
ip address
  ip route-static
      ip route-static  //for SBC in IMS network
From the above configuration, we can see the next hop to SBC from AR is, but the next hop to IP Phone( is We had asked the customer many times to provide the detail topology of the network, but had no result.

For test, we asked the customer to add one more static
ip route-static  //for IP Phone

Then the other end can hear local end. The problem was resolved.
In this situation, we don’t know exactly the detail network topology. But we can try some solution to test it.

Root Cause

1) The peer address is not correct.
2) The IMS network drops the voice traffic sent from AR
3) The route between AR and IP Phone is not reachable


To make the voice call, it is a basic rule to make sure the route between two IP Phones is reachable.