You should need to use fragmentation in the frame-relay map-class if your CIR is slower than about 768kbps.
About your second question... are you referring to "anti-tromboning" where if a call is transferred or forwarded back out the same path as the originating call leg, that 0 bearers will be tied up instead of 2? I don't know that this is supported natively in the Q.SIG support in Cisco IOS yet, but if you have Q.SIG PBXs on both sides of the connection you could use the Transparent CCS feature to carry the signaling between the PBXs supporting this feature and it should work. See:
I read your answer, but I have a doubt related with the same issue, for example if I'm using 2 PVCs, one for data and other one for voice, why can I need to use fragmentation at both PVCs? I'm asking you because I already made some tests, and I can verify that, if take out the fragmentation from voice PVC the quality goes worst (when the link is partly full), could you please explain me?
Whether or not you need to do any kind of fragmentation has nothing to do with the number of PVCs or the CIR. It has everything to do with the actual circuit speed. The lower the circuit speed (the cut-off tends to be anything less than 768kbps) then the longer it will take to serialize large data packets that have not been fragmented -- e.g. a 1500 byte data transfer packet.
While the large packet is being serialized and placed onto the wire for transmission, the voice packet(s) has been waiting for so long that the far end has no voice to output to the other party on the call. And since this is going to occur in a staggered fashion, the interarrival time for the voice packets is not going to be the same. Instead of having a packet arrive every 20ms for example, you will get one at 20ms, another one at 30ms, another one at 200-300ms, another one at 20ms, etc. This is jitter.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...