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!

Avaya SM and SBCE with Sip Trunks

Status
Not open for further replies.

Bonker1974

Technical User
Oct 11, 2011
359
BS
Hi All,
I have this issue We are configuring SIP trunks on our Avaya CM 8.0 but are having issue receiving calls
With the SIP trace I can see the incoming call from the SBCE to the SM. But I'm getting a TLS error between the SM and the SBCE.
The connection between the Sm and the SBCE is configure for TCP.
Below are the SM trace



15:50:37.890 │──INVITE──►│ │ │ (2) T:2426032920 F:2423027835 U:2426032920
15:50:37.891 │◄──Trying──│ │ │ (2) 100 Trying
15:50:37.893 │◄──Forbidd─│ │ │ (2) 403 Forbidden (TLS Required)
15:50:37.894 │────ACK───►│ │ │ (2) sip:2426032920@172.16.103.54:5060


Call-ID: 8829534b8fc609708e9cc66f6e2de634 │
│CSeq: 525159931 INVITE │
│From: <sip:2423027835@172.16.103.55>;tag=24.51.100.100+1+7b666f61+52846d05 │
│To: <sip:2426032920@172.16.103.54:5060>;tag=14477144099580985_local.1565157285143_6312505_63125│
│28 │
│Via: SIP/2.0/TCP 172.16.103.55:5060;branch=z9hG4bK-s1632-000515979730-1--s1632- │
│Av-Global-Session-ID: 03f54130-396b-11ea-babf-000c29159aac │
│Server: AVAYA-SM-8.0.0.0.800035 │
│Content-Length: 0



Leadership determines the direction of the company. Organization determines the potential of the company. Personnel determines the success of the company.
 
I've not had this particular issue and my experience would be from another system, but the TLS errors I got there constantly stemmed from certificate issues.

Do you need to install certs on the SM and SBCE? I'm not sure if you do, but a thought.

I'll be following for resolution, curious what it is.
 
I have not had that issue either but could be a certificate issue or check you adaptations as well could be a problem.

You may try changing from TCP to either UDP or TLS and see if this will resolve the issue.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top