BCS Conference Bridge not working

[Anonymous]

Trying to set up the Conference Bridge on the UC/BCS,

When I call 7050 on the 7100 the call connects to the UC and I hear a cut off audio file.  At this point the 7100 must go into proccesor overload because even pings go from 1 msec to 500 and timeout.

7100 A4.12 UC 4.5.3

[Anonymous]

restarted the UC server and it works now.... is this normal?

[Anonymous]

Brian,

Here are the steps needed to configure the conference bridge in a BCS setup taken from :

• Create a new communication system.

• Create a SIP trunk for the NetVanta 7000 Series unit to properly route calls destined for the audio conferencing system.

• Create a dial plan entry in the NetVanta 7000 Series unit to route calls through the new SIP trunk.

Is the bridge configured to go over a separate SIP trunk to UC?  If so could you strip out any sensitive information and attach your configuration?  The output from a show proc cpu as well as debug sip stack messages and debug voice verbose when the problem happens would help us too.

Thanks,

Matt

[Anonymous · Accepted solution]

That was all done but nothing worked until a restart.

[Anonymous]

Brian,

Make sure that ip rtp symmetric-filter is enabled on the 7100.  If it happens again it would be helpful to get the outputs requested above as well as a packet capture from the UC server.  Also, see if restarting the ADTRAN NetVanta UC Server SIP Service Manager service fixes the issue instead of a full restart.

Thanks,

Matt

[Anonymous]

What is ip rtp symmetric-filter?

Message was edited by: matt - removed personal contact information

[Anonymous]

The command ip rtp symmetric-filter enables filtering of received nonsymmetric RTP packets.  When enabled, any packets that don't match the source IP and port in the received SDP will be dropped.  It should always be enabled except in very rare cases where some SIP devices send from a different port than they receive on.

Thanks,
Matt

[Anonymous]

Since I branched your reply to a new discussion your confirmation of the filter being enabled was removed from this thread.  If the problem happens again we will need to see the output from the debugs listed above along with the packet capture.

Thanks,
Matt

[Anonymous]

Thanks Matt

Message was edited by: matt - removed personal contact information