Hi All,
This query is regarding CONTENT ID misconfigured in sipxrls.log for the
speed dials with presence enabled. The following case explain in details:
Polycom(122) monitors 121(Polycom) and 123(SMC3456).
The sipxrls.log must show the content ID for 121 as CONTENT-ID:
<[email protected]>
and for 123 as CONTENT-ID: <[email protected]>
<resource
uri=\"sip:[email protected];sipx-noroute=VoiceMail;sipx-userforward=false\">
<name>121</name>
<instance id=\"consolidated\" state=\"active\"
cid=\"[email protected]\"/>
</resource>
<resource
uri=\"sip:[email protected];sipx-noroute=VoiceMail;sipx-userforward=false\">
<name>122</name>
<instance id=\"consolidated\" state=\"active\"
cid=\"[email protected]\"/>
</resource>
Irrespective of either of the monitored phone(121/123) being busy with
other user. In this case both the IDs should be displayed along with
details of call conversation.
But in recent build the content ID for second user is also displayed as
CONTENT-ID: <[email protected]> ignoring the CONTENT-ID:
<[email protected]>.
Example:
1. From any SCS registered phone dial 121, answer the call.
2. BLF appears on 122 for the busy user121. Hang up the call.
Verify in sipxrls log:
For user 121 the content ID is displayed as 0 with other call details,
CONTENT-ID: <[email protected]>
<resource
uri=\"sip:[email protected];sipx-noroute=VoiceMail;sipx-userforward=false\">
<name>121</name>
<instance id=\"consolidated\" state=\"active\"
cid=\"[email protected]\"/>
</resource>
Here the CONTENT-ID: <[email protected]> for second monitred phone(123)
is missing.
Similarly, when 123 is busy with other phone the following is displayed
in sipxrls log
CONTENT-ID: <[email protected]>
<resource
uri=\"sip:[email protected];sipx-noroute=VoiceMail;sipx-userforward=false\">
<name>122</name>
<instance id=\"consolidated\" state=\"active\"
cid=\"[email protected]\"/>
</resource>
supposed to be the content ID as 1.
Please suggest me whether this change is done intentionally or is it a
wrong behavior.
-Rashmi Ratkal
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
