Mossman, Paul (Paul) wrote:
Vani wrote:
In total I feel at Step 4, the phone1 TUI should display appropriate messages.
Please let me know if you have any questions.
The phone1 will always display the From: header value of incoming INVITE.
There's nothing we can (or should) do about that.
Okay. This means, when P1 calls P2 using click to call. All till the P1
answers to the invite coming from sipxconfig, P1 will display
"Call From P2". This is confusing but it appears that there is no way out..
For a click-to-call 127, can you think of a From: header value more appropriate than
"127"?
(Keep in mind that we would have difficulty localizing this string.)
Could it be possible /Not to display any message on P1's TUI/, till P1
answers to the invite coming from sipxconfig.
That is,
P1 calls P2 by click to call.
as soon as P1 hits click to call button on sipx config UI, an invite is
sent to P1 from sipxconfig.
P1 answers to this invite.
All till this time there is no message displayed on P1's TUI.
Here onwards, P1 displays "To P2" and call proceeds.
Not sure whether the above can be made to work. This is my guess :)
Thanks,
Vani
Please let me know if current behavior is the best behavior that is the
way in which click to call works, in that case, this thread may safely
be ignored.:)
-Paul
[email protected]
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
