IPOffice 9.0.4 and Scopia Elite 5000 as sip client 3

[MikeTheSpike]

Hi All,

I just recently setup IPOffice 9.0.4 Server Edition and I am trying to interconnect this with Scopia Management ver 8.3 and a Scopia Elite 5110 MCU.

What I am failing to do is to register the Elite 5110 MCU with IP Office as a sip user as is suggested in the deployment guide for Avaya Radvision products.

The Elite is trying to register with the username "Elite-192168000150" as can be seen from the trace below:

16:29:20 29049859mS SIP Tx: UDP 192.168.20.5:5060 -> 192.168.0.150:5060
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.0.150:5060;branch=z9hG4bK-5b754-16542264-4edbea40-7062c1a0
From: <sip:Elite-192168000150@192.168.20.5>;tag=7070c170-c0a80096-13c4-6009-5b754-3201e9e6-5b754
Call-ID: 143fcab0-c0a80096-13c4-6009-5b754-491b52db-5b754
CSeq: 1 REGISTER
User-Agent: IP Office 9.0.4.0 build 965
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SU BSCRIBE,REGISTER,PUBLISH
Supported: timer
Server: IP Office 9.0.4.0 build 965
Reason: Q.850;cause=21;text="Call rejected"
To: <sip:Elite-192168000150@192.168.20.5>;tag=3b2403bdcee28d05
Content-Length: 0


The IPOffice username field does not allow me to create a corresponding SIP user with the name "Elite-192168000150" as the field concatenates the last three letters of the username i.e. 15 characters max and the SIP username seems to be hardcoded into the Scopia Elite 5000 series MCUs in the combined form of "Product Identifier - IP Address"

Is anyone able to assist me with some guidance on how to achieve this?

Many thanks

Mike

 

[holdmusic34]

It sounds like you don't have the IP Office version....You have the IP Office version if you see Avaya in the top left of the Administration screen. If it says Radvision it's not the IPO version.
Also, make sure you give the user a log in password in User> telephony. Keep it the same as the user password while you're working on it.

I hope this helps.

Dulce et decorum pro Avaya mori

 

[shardian]

I think there is a difference in what you need to do based on the product. Holdmusic has shown above how to register an XT5000 which is different to an Elite bridge product.

From memory the bridges don't register as an extension, and instead you use a trunk to connect the two, whereas the endpoints (xt5000, xt240 etc) would register as a SIP extension.

Take at look at this as it defines the method to configure the trunk between bridge and IPO:

http://marketingtools.avaya.com/kno...on/index.htm?large_enterprise_deployment2.htm

 

[MikeTheSpike]

Holdmusic, thanks, I have read and reread that doc and followed those steps, but I am still confused.

I have managed to successfully connect the Scopia XT5000 SMB9 unit without any problems using the guide you provided. Works well!!

shardian has it right in that I am using a Scopia Elite 5110 MCU ver 7.7.6 (192.168.0.150) tied to Scopia Management (iView) 8.3 (192.168.0.151) and IP Office 9.0.4 (965)(192.168.20.5). The Scopia Management server is all in one server i.e. Scopia Desktop Server, ECS and iView

I have come across some info that suggests the Scopia Elite MCU uses both H.323 and SIP connections to the Gatekeeper/ECS (H.323) and the SIP B2BUA of Scopia Management Server and does not register with the IP Office as a user. It appears that the default SIP domain is the only part that is pointed to the IP Office IP address. This seems to be the main difference between the Elite MCU and the XT5000 MCU in the way it registers. Is this due to the fact that only a single conference at a time is supported with the XT5000 and multiple multipoint conferences are supported with the Elite, and as such it must be used as a trunk instead?

I have configured the Elite with H.323 enabled and pointing to the Gatekeeper (192.168.0.151) as well as the SIP protocol with the SIP server IP address of the SIP B2BUA (also 192.168.0.151) and the SIP Domain pointing to the IP Office (192.168.20.5)

I have added the IP Office as a SIP server in Scopia Management

In IP Office I have enabled the SIP Trunks and created the SIP trunk back to Scopia Management.



I'll come back and edit this further in a few minutes.

 

[MikeTheSpike]

As soon as I can figure out how to edit threads and get the images working I'll be back.

I have tried inserting picture and supplying the dropbox link, but its not working.

 

[holdmusic34]

I'll get back to you in about 12 hours when i can check the docs.
In the meantime, to show images, change the dropbox link from

http://www to

dl as per below. Also, drop the ?dl=0 at the end of the link.

https://www.dropboxusercontent.com/s/3zg5vlvv069u209/radvision3.JPG?dl=0
https://dl.dropboxusercontent.com/s/3zg5vlvv069u209/radvision3.JPG?dl=0

then click the picture icon above your response and insert the link in there.

Dulce et decorum pro Avaya mori

 

[holdmusic34]

What happens if you tick use registrar?
Can the IPO register the SIP trunk? Monitor?

Dulce et decorum pro Avaya mori

 

[MikeTheSpike]

Alright, thanks for the help Holdmusic! Here are my steps.

13:47:13 5411910mS SIP Tx: UDP 192.168.20.5:5060 -> 192.168.0.151:5060
OPTIONS sip:192.168.0.151 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.5:5060;rport;branch=z9hG4bK5f44fd5565012738a37844dea23c0603
From: <sip:192.168.20.5>;tag=a229a028feba2d8e
To: <sip:192.168.0.151>
Call-ID: ff4ddfacb49e13b7fc9447e5826baa46
CSeq: 1389390310 OPTIONS
Contact: <sip:192.168.20.5:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 9.0.4.0 build 965
Content-Length: 0

13:47:13 5411933mS SIP Rx: UDP 192.168.0.151:5060 -> 192.168.20.5:5060
SIP/2.0 200 OK
From: <sip:192.168.20.5>;tag=a229a028feba2d8e
To: <sip:192.168.0.151>;tag=aedac38-0-13c4-55022-d5d26-7bff5508-d5d26
Call-ID: ff4ddfacb49e13b7fc9447e5826baa46
CSeq: 1389390310 OPTIONS
Via: SIP/2.0/UDP 192.168.20.5:5060;rport=5060;branch=z9hG4bK5f44fd5565012738a37844dea23c0603
Allow: INVITE,ACK,CANCEL,BYE,INFO,UPDATE,REFER,NOTIFY,SUBSCRIBE,SERVICE
Content-Length: 0


From the 200 OK above something is happy.

Now the interesting thing is that I can place a SIP call directly from Polycom RealPresence for iPad (not registered) to the SIPB2BUA by ipaddress and it connects me into the IVR of the Elite MCU, so the SIP call bit is partially working for Scopia side. The strange thing is that the call does not show up in Scopia Management and there are no SIP logs in the SIP log directory either. In actual fact I have no logs in the SIP folder at all.

Is this normal?

I will play with the Use Registrar switch and let you know what happens

 

[Westi]

never knew that you can do that with Dropbox, have a star for providing the info on how to do that holdmusic34

Joe W.

FHandw, ACSS (SME), ACIS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[holdmusic34]

OK. I checked the docs but he LAB doesn't go through the SIP component. It only concentrates on the H.323.

However,

1) Your IP Office SIP trunk is set up by the book.
2) Your SIP trunks have registered! Have you restarted the management server to see if it's being a prick?

3) You've done this part but check it again:
Configure the Elite Series MCU with details of the IP Office as the gatekeeper/SIP proxy.
To configure the Scopia MCU
1. In the Scopia Management configuration menus, select Resource Management | Gatekeeper/Sip proxy.
2. Select Add and enter details that match the IP Office and its SIP settings.

5) Continue on with the steps from [URL unfurl="true"]http://marketingtools.avaya.com/knowledgebase/businesspartner/ipoffice90en/mergedProjects/radvision/index.htm?large_enterprise_deployment2.htm[/url] including adding a short code

6) Escalate to Disti.


NOTE: H.323 and SIP users are only required for the XT5000 and XT4200 endpoints (to join in to the major Radvision MCU)


Dulce et decorum pro Avaya mori

 

[holdmusic34]

You put an IP route in the IPO for the SIP trunks right?

Dulce et decorum pro Avaya mori

 

[amriddle01]

To wander slightly off topic..... you don't need to edit your Dropbox links if you put the pics in your public folder, just copy the link and post, that's all I ever do

 

[Gunnaro]

Andy, Dropbox accounts created after late 2012 does not have a Public folder.
Those account need to use the method mentioned by Holdmusic.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[MikeTheSpike]

I guess, what I am trying to do is this:

You can find it here:

http://docs.radvision.com/bundle/rv_solution_guide_8/soln_sg_integr_with_avaya_IPOffice_Centralized

Now I need to find out what the settings must be for this to work, since it is documented as working since release IP Office 8.1 and Scopia Management ver 7.7 and later.

It seems as though the documentation is incomplete and this has not been remedied even into the new IP Office 9.1 release.

I managed to work on the Scopia Management server and Elite 6000 of my disti a day ago and saw that the MCU was completely registered (H.323 and SIP) to the Scopia Management server address and that the indicators for the following on the status page were green: Gatekeeper, SIP Server and Scopia Management. They don't have IP Office connected so I cant use them to get any idea of the configs I need.

So I set the Elite 5110 MCU to register with the B2BUA:

I have run wireshark traces on the Scopia Management server and see the Elite MCU H.323 registration is accepted but the SIP registration is rejected.

I guess that is why I get this:

Since there is a SIP response in the trace (even though it is a rejection), does that mean the B2BUA is present and working the way it should?

How do I test this?

Anyone with any further advice on what needs to be done to get this working?

 

[MikeTheSpike]

200 OK

Here's some IP Office to Scopia Solution dope.

Your IP Office is setup with a trunk pointing to the Scopia Management address.

Then create a user:

You will get:

and this:

My Precious! Have a good weekend!

 

[holdmusic34]

Top stuff man!

"There is one hope, and, as usual, it's Norwegian!"
Professor Farnsworth, Futurama