Firmware 1.3.0 (Build: 2532) Problem

<< < (2/3) > >>

RonR:
Quote from: jimates on September 10, 2011, 02:40:02 pm

Quote from: RonR on September 04, 2011, 09:10:34 pm


The Peer Number received by the OBi100 (300123456) is that of the incoming call and not the OBi110 forking the call, causing Circle of Trust to fail.


This is the main reason (feature) many have been waiting for release 1.3. We want the caller id to be for the original call.


You misunderstood.

From the release notes:

- Allow Caller-id spoofing for calls bridged via OBiTALK service. But use the obi number for circle-of-trust authentication.

The OBi number is NOT being used for circle-of-trust authentication in the case I cited.  The bridged call's CallerID is being used which, of course, does NOT match the circle-of-trust authentication.  It works correctly with the forks ordered one way but not the other -- one of them has to be working incorrectly.

(And I guess the reboots at the end of every call were simply thrown in for additional entertainment.   ;D)

earthtoobi:
Ronr: i see that a lot of posts from users that seems  repetitive.it would be nice if someone can collate the issues/questions till now and reference the resolution threads for each.
it would be a nice FAQ that people can read before they post.

jimates:
Many items are addressed in the stickies of each sub-forum, no one reads them before they post.

obi-support2:
RonR:

1. Reboot problem as described in 2532 is reproducible. This has been addressed and
    the fix will be included in the next f/w update
2. Caller-ID and COT authentication in OBiTALK service should work as advertised.
    Please make sure your OBi100 is also updated to ver 1.3 in order for the
    COT authentication to work properly

Thank you.

RonR:
Quote from: obi-support2 on September 15, 2011, 07:15:55 pm

2. Caller-ID and COT authentication in OBiTALK service should work as advertised.
    Please make sure your OBi100 is also updated to ver 1.3 in order for the
    COT authentication to work properly


The OBi100 has not been updated to v1.3.  Even so, why does the forking order of the calls in the OBi110, only one of which is directed to the OBi100, cause COT to behave differently?  I could understand if it didn't work at all, but it works correctly with certain forking orders and not with others.

Your comment also infers there is an interoperability problem between v1.3 and prior versions.

Navigation

[0] Message Index

[#] Next page

[*] Previous page