|
Sort Order:
I also tried to configure a SIP User account and IM User account using the Provisioning method.
I used SCS Build 4.1.6-017791 2010-01-26 I created a SIP User that was a member of a group that had Instant Messaging enabled The SIP User account on the Nortel 3456 was created The IM/XMPP Account was not even created on the Nortel 3456 The IM/XMPP user was seen in Openfire GUI I then manually added the IM/XMPP user to the Nortel 3456 and it created and worked as expected It seems the issue here is that the IM/XMPP user is not sent to the Nortel 3456 using the Provisioning method. I then looked at an older Build of SCS 4.1.6-017729 2010-01-19 (Ottawa Live Trial Build) I connected my Nortel 3456 to this SCS and the SIP Account and the IM/XMPP account were both created as expected. I then compared the Nortel 3456 ini files from both systems and saw that on the system when XMPP account failed to be created it was #10 in a list of 10 proxies where proxy0 was the SIP account and proxy10 was the XMPP account. On the system where the XMPP account was created successfully it was #1 in a list of just 2 proxies, SIP Proxy0 and XMPP proxy1. Added both ini files called chris_test_ini_files" Agreed, it looks like a profile generation issue. (sipXconfig.)
Reverting this JIRA to the original issue. The 2010-01-27 update is a separate issue (probably due to revision 17800), and should be handled in a separate JIRA.
This issue is probably related to revision 17769, which changed how the proxyN values were generated. As Chris pointed out above, the XMPP account used to occupy proxy10.
When fixing this issue, please update the unit tests so that the generated profile contains an XMPP account. (Suggestion: Do the unit test first, then re-factor the code until the unit test stops failing.) Please note that SMC (CounterPath Bria) provisioning is currently broke in ISO istalls due to
Posted a patch (0001-xx-7484-changed-proxyN-generation.patch) for this issue.
Changed the way proxyN is generating in the ini file of the SMC phone. Now, first are generated the sip lines, then the xmpp lines and then lines are filled with enabled="false" in order to stay consistent with the solution for xx-7406. Also changed the number of maximum lines for SMC in sipxconfig UI from 10 to 5, so SMC phone could have maximum 5 sip lines and 5 xmpp lines (total of 10 lines supported by SMC phone) as Paul suggested. Hi Huijun, please review and apply if OK. Thanks.
I am not sure if there is an agreement with PLM to change maximum lines from 10 to 5. What if customer only have SIP accounts, and they should be able to create maximum lines, which was 10?
Good point. I will talk to Ian about it, but in the meantime could you commit the change?
Changing the maxline for SMC from 10 to 5 on sipXconfig UI has been agreed by PLM, the patch is committed.
I am still seeing this issue it does not seem to be fixed in Build 4.1.6-017927
To be verified after
Verified the issue in build 4.1.6-018078.
SMC phones registers successfully with IM account and able to chat with other users.Hence closing the issue. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Closed
Major
SMC phones does not register with IM account in build 4.1.6-017776 
1- If you log into the openfire web portal directly (port 9094), do you see user 200 created?
2- Can you please attach the SMC configuration file that sipXconfig generated?
3- The SMC logs do not have any XMPP-related entries. Can you double-check that you have enabled the "Maximum" logging for the XMPP sub-component?
4- Are you able to register account 200 from pidgin?
Thanks