SV9500- Background noise sound for calls via E1 PRI Trunk 1

[hcmbmt]

Hello all,
Is there anybody have face to this issue before?
A background noise sound during conversation from either NEC IP Phones or 3rd Party SIP phone via E1 PRI trunk.
The attached file for reference. This sound is similar with the Alarm warning sound of SV9500 itself.

 

[DoubleDriveLine]

I have never had that issue but I have had issues before with PRI that only got fixed by busying out the card and removing it from the system. Wait 30 seconds then install it again.

If you are doing trunk side recording you may want to disconnect it to see if that is the source.







There are 10 kinds of people in the World.

Those that understand Binary and those that don't.

 

[hcmbmt]

@DoubleDriveLine:
I tried to test and all have same issue (background sound)
1. Connect SV9500 to SV9100 via PRI card (either Networking Mode or User mode)
2. Connect SV9500 COT to SV9100 Analog extension Card.
Maybe the problem comes from IPPAD configuration?

 

[sto933]

Do ypu mean clicks heard on this recording? If yes then it sounds like sync slips to me. Does your system properly sync'ed with PRI provider?

 

[hcmbmt]

@sto933
Yes, the clicks sound on the recording. If the problem comes from "sync" of PRI provider then I cannot explain why calls via Analog Trunk also has same issue.

 

[DoubleDriveLine]

I assume you don't have any TDM phones. If you hear the clicks on the TDM phones then the IP Pad card is probably the issue.

Which PAD cards do you have and what firmware are they?



There are 10 kinds of people in the World.

Those that understand Binary and those that don't.

 

[hcmbmt]

@DoubleDriveLine,
Yes, I dont have any TDM phones, 100% IP phones (NEC & SIP phones). The IPPAD A card information:

Circuit Card Name CH-IPDA
+------------------+
| Firm Name/Issue |
+------------------+
| SP4045 IPDA A |
| SP4046 IPDBOOT A |

 

[DoubleDriveLine]

What are the softswitch settings for the pad card?

Do you have data in ALOCL and AIVCL?





There are 10 kinds of people in the World.

Those that understand Binary and those that don't.

 

[hcmbmt]

@DoubleDriveLine,
I added the setting file here. The sound like a warning tone but dont know what it is. I already disable the RTP warning tone in ASYDL, SYS 1, Index 813, Bit 5 = 1.

 

[hcmbmt]

Update here,
Thank you all for your kind support.
The problem comes from ASYD, SYS 1, Index 91. I changed it to default "00" and it fixed the issue.

 

[DoubleDriveLine]

That would tell me you turned off your clock source to the TSW. So there was a clocking issue and should still be one.

If this is all you have for location groups it is not complete and your QOS values are not right.

In ALOCL the Setting of Type of Signaling Packet Service should not be higher than the RTP packets. These are the control packets which are not as critical. A DSCP value of 26/28 or IP Precedence of 3 would be the norm. This would be the same for all location groups. This command only affects control packets not voice packets.

In ALOCL if you only have this one group defined it is a very small subnet. If you phones or end devices are outside of that group they don't fall into a location group and the system will just use the default G.711 40ms setting with no QOS.

What I normally do is set a blanket over the possible private IP address ranges.

0.0.0.0/32 Location group 0
192.168.0.0/16 location group X
172.16.0.0/12 location group X
10.0.0.0/8 location group x

NEC says you need to have a location group for each range. I have found that you can make X the same location group number and it functions fine. It is however not supported. This blanket will cover anything that connects to the network unless you devices that will be public IP Addresses. Those would have to be added additionally.

In AIVCL

Create an entry for location group as below. Follow the same pattern if you have more than 2 groups. The inverse of these groups is automatically created.
0 to 0
0 to 1
1 to 1


Set your Setting Type of Voice Packet Service to

DSCP 46 or IP Presedence 5

That is what provides QOS to the voice packets. With out it you have no QOS.

For your codecs you can drop the 40ms packet setting. It will only confuse things if you ever go to SIP trunks. SIP trunk providers only accept 20ms packets so it doesn't make sense to support anything else internally. Just make everything 20ms packets. These is not an issue with this part of your settings unless you move to SIP trunks.

I normally turn on echo canceller A to B and B to A. In truth I started doing that because I had a location that one of their remote sites had an issue with echo. I had to turn it on and then wait to do the reboot or reset the IP connections.

Attached is a document listing the QOS TOS values. It shows how they all relate to each other and what function they play.

And on another QOS note if QOS is not turned on within every switch at the site the QOS tags get stripped from the data packet passing through the switch.

Remember after setting ALOCL and AIVCL Nec says you must reboot the system to affect the change. There is also another command that will reset the IP but I normally do the reboot.













There are 10 kinds of people in the World.

Those that understand Binary and those that don't.

 

[hcmbmt]

@Doubledrive Line
Really appreciate for your very detail suggestion.
I have changed the setting follow your advise. Attached file is the setting. Please help to correct if anything wrong.
I'm not so familiar with SV9500, please help to advise me some more thing:
1. What happen if turned off the clock source to the TSW? Will it effect to the system operation?
2. The IP phones are connected to different VLANs.
There is no problem for internal calls between VLANs and outbound calls from phones in same VLAN with PBX also no problem. But One-way audio for outbound calls via E1 trunks - Outside callers can hear us but we are not.
It seems like the problem comes from the network setting due to RTP packages are not delivered. What is the RTP range port to open on network? Or which setting we should check for it?

 

[DoubleDriveLine]

Those settings for AIVCL and ALOCL look better. I normally would not break out anything in the specific ranges like you did unless there is a reason to change codecs or payloads between groups. That just doesn't happen anymore (thankfully).

10.0.0.0/8 is the same as all of the 10.25.x.x groups you assigned. Remember we are only defining a range of IP Addresses that appear in the group. The NEC system is not concerned if X or Y address is the network address or broadcast address. Again the way you did it is fine it is just more steps than is necessary.

The fast answer on RTP is

This is from 165798-001-13-0--SV9500-PED_MLT-V9.pdf chapter 3 IP Phones. You definitely have a network issue as in routing or firewall between VLANs.

5.Self Port Settings Sets each port for DT830G. - - -
1.RTP Self Port Sets RTP port for DT830G [1024-65520 (except
59986-60000)].
Note 29,
Note 30
default 3462

Note 29: Odd numbered ports cannot be assigned.

Note 30: A unique number must be assigned to each of the following ports. For RTP Self Port, 16
ports starting from an assigned port are used.
• RTP Self Port
• SIP Self Port
• Push Server Port
• IPM Self Port







There are 10 kinds of people in the World.

Those that understand Binary and those that don't.

 

[hcmbmt]

Thank you DoubleDriveLine. I will update if there is any good new.