New 1032 Firmware Issue
Boykin:
Quote from: ianobi on April 30, 2015, 07:37:14 am
Quote
I found something that might have caused an issue. In OBiPlus I was using codec B, but the SP was using codec A in the 202. I changed OBiPlus to codec profile A. I will test this when I get home.
I believe that there is a bug with the way OBi devices negotiate codecs when setting up a bridged call. In your case I don't think it's a problem with which codec profiles are used, it's a problem with which codecs are actually enabled and their priority within the profiles. I managed to get around the bug by only enabling codec G711U in both devices. You may wish to try this as a test.
My setup does not include OBiPLUS, so I cannot comment on how that might affect codec negotiation when bridging calls. However, my problem did include an OBi1032 and an OBi110 and a bridged call between them.
You are correct. I turned off all codecs except G711U and now the latest firmware works. I can hear the caller and they can hear me.
When I bypassed the 202 and put a GV line on 1032, it works correctly too.
Even using only G711U, the auto attendant still does not work correctly. I can hear caller, but they still cannot hear me.
WelshPaul:
Quote from: Boykin on April 30, 2015, 11:43:06 am
the auto attendant still does not work correctly.
I reported the auto attendant issues a while back also. They should be working on a fix.
Boykin:
The offending codec is G726R32. I enabled the ones I had disabled one by one until I reproduced the problem. I had to disable this codec on the 1032s. The 202 has this codec and all the other default codecs enabled. I tried to disable this codec on the 202 and leave it enabled on the 1032s but that did not fix the problem.
Navigation
[0] Message Index
[*] Previous page