Looking to traces on MRA multi lines phone registration, i don't see second or tertiary lines numbers on the registration process (on the REGISTER message specifically)?
Does someone knows how those secondary and tertiary lines get register?
Jabber uses the primary extension assigned to end user for registration.
Even in multiline, only primary extension is used for registration.
The other remaining extensions are handed over to Jabber during the
authentication process with cucm/ldap through the device configuration file
(in this case the device is jabber).
2017-04-04T10:40:50.628+04:00 EXE01-V traffic_server:
UTCTime="2017-04-04 06:40:50,628" Module="network.http.trafficserver"
Level="INFO": Detail="Receive Request" Txn-id="15723" Src-ip="22.214.171.124"
Src-port="56258" Msg="GET https
2017-04-04T10:40:50.661+04:00 EXC01-V traffic_server:
UTCTime="2017-04-04 06:40:50,661" Module="network.http.trafficserver"
Level="INFO": Detail="Receive Request" Txn-id="30835" Src-ip="127.0.0.1"
Src-port="34444" Last-via-addr="10.80.50.25" Msg="GET http://vcs_control.testdomain.com:8443/qwe2emwk32hlbGZkcmlsbGlFbNxeRuZy5jb2e0EdwvaHR0cHMvdfewZHhdiY2NtMD4nz1sS7Etdi5zaGVsZmRyaWxsaW5nLmNvbS82OTcy/CSF1300.cnf.xml HTTP/1.1"
The primary extension is obtained before these messages during the login
2017-04-04T10:40:50.417+04:00 EXC01-V traffic_server:
UTCTime="2017-04-04 06:40:50,417" Module="network.http.trafficserver"
Level="INFO": Detail="Sending Response" Txn-id="30831" Dst-ip="127.0.0.1"
Dst-port="34986" Msg="HTTP/1.1 200 OK"
2017-04-04T10:40:50.422+04:00 EXE01-V traffic_server:
UTCTime="2017-04-04 06:40:50,421" Module="network.http.trafficserver"
Level="INFO": Detail="Sending Response" Txn-id="15721" Dst-ip="126.96.36.199"
Dst-port="56258" Msg="HTTP/1.1 200 OK"
Jabber client logfile
2017-04-04 10:40:50,278 DEBUG [0x00003c28] [netutils\src\http\
2017-04-04 10:40:50,281 DEBUG [0x00003c28] [l\ucm-config\uds\
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<description>Mohammed Al Baqari</description>
**** Please remember to rate useful posts
Yes, i understand that provisioning on CUCM is by downloading a configuration file. My question is on Line registration, not on line provisioning.
AFTER PROVISIONING, Device needs to register a line. If device does not register a line on call engine (using any means), it can not receive calls on that line. Also during a call that line needs to be updated (to reflect call status).
Is the problem that the additional lines do not appear when Jabber is registered via MRA? (But do appear when logged in on-prem?) If so, the problem may be MRA version rather than a Jabber/CUCM issue. I seem to remember that you need VCS/Expressway X8.10.1 or later for Jabber Multiline. Certain handsets had MRA Multiline support as early as X8.9, but Jabber multiline support was later.
Roger that. The last time I set up Jabber Multiline via MRA I noticed that calls outbound to the Jabber client made to any of the 8 lines in CUCM all went to the primary line on Jabber client, while inbound calls from the Jabber client could come into CUCM from any of the lines on the client. It may be (theorizing here) that only the primary line actually registers and the other lines are seen akin to alternate extensions when in MRA mode. That said, different Jabber/CUCM/MRA version combinations may give different results.
I'd say "HTH" at this point, but I suspect it doesn't....lol