Avaya Knowledge - CM: No audio on both parties on-call

Details

CM: R016x.03.0.141.0

SP: 03.0.141.0-22890

Problem Clarification

This is a new "campaign" for customer and they added new 1-CLAN and 2-medpros on NR 36 and 37. They also build trunk-groups 9 - 18 (except 15) for all incoming and outgoing calls for this campaign.

They are experiencing no audio on both parties (external calls only) for all inbound and outbound calls. There is no issue for internal extension to extension calls. This is affecting 100% of external calls.

Cause

As seen on list trace station, when I asked customer to call-out CM is sending the calls to trunk-groups 2 and 3. I checked the route pattern and these trunk-groups are indeed defined in the route pattern. This is point 1 that I raised to BP.

Next is, phone is in NR11 and the medpro is in NR3. Since this is affecting 100%, I checked the NR config and confirmed that codec is set properly between these 2 NRs. Then, I move on checking the connectivity of these 2 equipment / IP on network side by issuing ping and this is what I got.

ping ip-address
                          PING RESULTS
End-pt IP                             Port   Port     Result Time(ms) Error
                                               Type                       Code
172.18.0.93                            03B07   IPMEDPRO FAIL             2805
172.18.0.93                            03B07   IPMEDPRO FAIL             2805
172.18.0.93                            03B07   IPMEDPRO FAIL             2805
172.18.0.93                            03B07   IPMEDPRO FAIL             2805
172.18.0.93                            03B07   IPMEDPRO FAIL             2805
172.18.0.93                            03B07   IPMEDPRO FAIL             2805
172.18.0.93                            03B07   IPMEDPRO FAIL             2805
172.18.0.93                            03B07   IPMEDPRO FAIL             2805
172.18.0.93                            03B07   IPMEDPRO FAIL             2805
172.18.0.93                            03B07   IPMEDPRO FAIL             2805

I discussed this with BP and they confirmed that these medpro (subnet) is not connected to the phone's segment on customer's network. This is how it is supposed to be since these 2 subnets belong to different campaign. As per BP, CM should not engage this medpro or any dsp resource on NR3 but instead should get resource on NR36 and 37.

I explianed to BP that CM engage medpro in NR3 because trunk-group 2 and 3 terminated to a G450 which is in NR3.

11:03:29 TRACE STARTED 10/21/2015 CM Release String cold-03.0.124.0-21754
11:03:41     active station      22873 cid 0x39cc
11:03:41     G711MU ss:off ps:20
             rgn:11 [172.18.0.93]:2048                              ========================> H323 phone
             rgn:11 [172.18.0.22]:2548                              ========================> medpro in NR11
11:03:44     term        cid 0x39cc
11:03:44     route-pattern 102 preference 0 location 1/ALL unavailable cid 0x39cc
11:03:44     dial 90143360236 route:ARS
11:03:44     term trunk-group 2      cid 0x39cc            ========================> DS1 is in G450 registered in NR3
11:03:44     dial 90143360236 route:ARS
11:03:44     route-pattern 102 preference 1 location 1/ALL cid 0x39cc
11:03:44     seize trunk-group 2 member 14    cid 0x39cc
11:03:44     Setup digits 0143360236
11:03:44     Calling Number & Name NO-CPNumber NO-CPName
11:03:44     G729A ss:off ps:20
             rgn:11 [172.18.0.93]:2048
             rgn:3 [10.21.2.54]:2134
11:03:44     Proceed trunk-group 2 member 14    cid 0x39cc
11:03:45     Alert trunk-group 2 member 14    cid 0x39cc

Solution

I suggested for customer to correct their route pattern and make sure they are sending the outgoing calls to the correct trunk-group. Once the correct trunk-group is involve then CM will engage the correct dsp resources local to the NR where these DS1s (of the trunk-group) belong.

I reminded BP that apart from connecting NRs via codec on ip-network-region form they also need to ensure that such subnets are connected on network side. They can simply execute a ping command on CM to ensure this.

Also below parameters can also be checked.

IP NR: IP audio hairpinning ? Y

Station: Direct IP-IP Audio connection? Y

Additional Relevant Phrases

Calls no audio Direct IP-IP