Hi,
we have a strange issue with our Jabber client.
All was working fine and suddenly outbound calls via a sip trunk started to have issues randomly (SBCs at the remote end are not controlled by me but are supposed to provide transcoding).
the best way I can describe it is as if the ringback had changed from the normal UK ringtone to a longer tone (or double tone for sensitive ears). Then call actually connects but drop as soon as they connect.
Jabber client is 8.3.1 but I have also tried with the latest one.
our CUCM is 11.5.
If you tick MTP required on the Jabber profile all work fine (we do not have MTP ticked on the Global sip trunk and we use RFC2833 for DTMF). We do not use a Cube.
It looks like our sip provider is proposing G711alaw, ulaw and G729 and we have our codec locked to G711alaw-so that could be an issue.
I have read somewhere that ticking MTP was forcing the user end to use oob signalling for Jabber. can somebody shed some light on this please ?
We would like ideally Jabber to work without MTP as it creates issues for call recording.
thanks a lot,
Greg
