Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Issues with metaswitch metasphere SIP line IP office Server Edition 10.1.0.1.0 build 3 1

Status
Not open for further replies.

Jmack23

Programmer
Mar 17, 2017
24
US
Hello,

I am having issues getting a SIP line to work with the Avaya IP office. The information I can find is only for version 8.1. I worked with the provider and they are seeing the system come up and register then when options request is sent it goes out of registration. Then spams options and fails. SSA shows the system registered and idle. I tried using the FQDN for the ITSP Domain name under SIP line and under transport ITSP proxy address. I have tried the IP address. Under Voip I have enabled Re-Invite Supported and PRACK/100rel Supported. DTMF is set to RFC2833. Under SIP advanced I have the Association menu "From" header hostpart against ITSP domain. I disabled the authentication on the SIP line in the metaswitch but it still is having the same issues.

Here is some images of the configuration. I also included some images for the metaswitch error messages.

Link

Has anyone configured one of these lines with a newer version of IP office?

Any help would be greatly appreciated.
 
 https://files.engineering.com/getfile.aspx?folder=6004c883-4e64-4f5d-8988-81150a7d2156&file=Metaswitch_7.1.1_Avaya_IPO_Config_Guide.pdf
Just in case anyone else has issues with meta switch. When you can get the system idle and registered to with the SIP authentication. Then you get the errors I was seeing the failed to respond to Options request its because you have the incorrect Association Method. The correct method was "By Source IP Address" and the Sessions Timers need to be set to "Re-Invite". I also had another issue where I needed to specific the licenses for the SIP trunk under the License>Remote server tab. You have to specific the reserve SIP trunk Sessions otherwise it will not allow calls even when the trunk is not utilizing any. I was seeing congestion count for this.

Sysmon shows it like this
12:34:21 344884467mS Sip: SIP Line (2): Incoming Call in excess of License: Consumed: 0, Available: 0

Hopefully this helps someone else out.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top