Again, more new, good information. I really appreciate all the feedback.
I modified the topology hiding and overwrote the FROM value with what the carrier wants to see. That definitely made a difference in the REGISTER request.
After the change, as Arslan mentioned, the first request returned a 401 Unauthorized. Then, a 200 OK came back. Excellent!
Making progress...
The next hurdle is making a call. After seeing the 200 OK, I placed a call. It didn't return a busy immediately; it was dead air for several seconds, then busy. I'll work with the carrier on that one and report back here.
Thank you all for your help.
------------------------------
Ted Hargiss
Manager
Landstar
------------------------------
Original Message:
Sent: 09-11-2020 01:14 PM
From: John Waber
Subject: SBCE Registration Request - SIP Carrier/Provider
Ted,
The SBCE's Topology Hiding feature modifies the domain portion of the SIP URI. Because almost all vendors want the domain to be expressed as an IP Address, the SBCE's default ("auto") option performs that change. It does a simple Network Address Translation (NAT) to swap the address between an internal IP address and an external Public address.
Avaya wants the domain portion of the address to be a "name", such as training.com. So the Topo Hiding section for traffic destined for ASM is usually set to "overwrite" to the domain name.
I believe that the Topo Hiding feature is what is changing the domain-name in your REGISTER request to an IP address.
While the Topo Hiding feature allows you to pick which headers are modified, it does not also allow you to be selective about which requests get that treatment.
Technically, the TO and FROM headers are "cosmetic" and have no effect on the routing of the message. So overwriting the IPs with domain-names in the outgoing message might work. This would be in used in the Topo Hiding configuration going towards your ITSP. Do not change any other outbound headers; only the TO and FROM. Good Luck.
------------------------------
John Waber
Senior Technical Instructor
ConvergeOne- Center of Excellence
Original Message:
Sent: 09-11-2020 11:10 AM
From: Ted Hargiss
Subject: SBCE Registration Request - SIP Carrier/Provider
Well, the good news is that the carrier is now receiving the REGISTER request from my SBC.
The bad news is that they don't like one thing they see.
In the Message Header's FROM field (captured from a trace), the address is <phone_number>@<my_internal_IP_address>. The carrier said that it should be the phone number and their domain name (what they've provided) like what is in the TO field. Essentially, the REGISTER request needs to reflect the phone number and their domain name in both the FROM and TO fields.
In the SBC>Server Configuration>Heartbeat section, the FROM and TO fields have the same thing - the phone number and the carrier's domain name (what they've provided). I don't know where else the FROM field can be changed so that when sent, it shows the carriers domain name. Any ideas?
------------------------------
Ted Hargiss
Manager
Landstar
Original Message:
Sent: 09-09-2020 02:13 PM
From: Ted Hargiss
Subject: SBCE Registration Request - SIP Carrier/Provider
Avaya SBC 7.2
I am trying to get SIP service working with a new SIP carrier and not having success.
The new carrier route has been built in the SBCE and the route is open on the router/firewall.
The carrier says that my SBC must register with their SBC before calls can be placed. They expect to receive a registration request that includes the PBX object (number) and credentials from my SBC.
Anyone heard of this and know how to send a registration request from the Avaya SBCE? I do not see it.
Thanks
------------------------------
Ted Hargiss
Manager
Landstar
------------------------------