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!

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

SIP connection between Session Manager and CM OOS/FE-Idle

Status
Not open for further replies.
fondog2

fondog2

Systems Engineer
Jan 19, 2006
338
US
7.0 Virtual (CPOD)
Never had this happen when building sip connections. Can anyone point me in the right direction to resolve this? The funny thing is I built the sip link to AAM and it is up so not sure why CM wouldn't link up.

Thank you,
 
Sort by date Sort by votes
TCP? TLS? Ports right?

Got DSPs in between the regions of that trunk? Got a traceSM of what's happening between CM and SM (with TLS negotiation cause you're on 7)
 
Upvote 0 Downvote
Yes this is a TCP connection. Yes I have a G450. No I didn't do a traces but I will see if it shows anything.
 
Upvote 0 Downvote
TraceSM shows remote host is not trusted. I looked at my entity links and they show TCP 5060 and trusted.
 
Upvote 0 Downvote
What about the SIP sig-group on the CM side is it on TCP 5060 as well?
 
Upvote 0 Downvote
Yes TCP. Looking further into the trace. It looks like it doesn't like something with the header. Now I have to figure out what it doesn't like about it.
 
Upvote 0 Downvote
check your SM SIP entity in System Manager and see if it has a default domain for port 5060. Check what the domains are in the sig group and the network regions to make sure they match.

Presumably a traceSM would show some options messages not be happy. If you stat the sig group, is it in service? Can you see a call from CM to SM try to get out and something about the domains doesn't line up?
 
Upvote 0 Downvote
Signaling group is showing group-state as far end bypass.
 
Upvote 0 Downvote
need that traceSM while busying and releasing the sig group
 
Upvote 0 Downvote
The traceSM shows nothing while busy and releasing the signaling group. Still shows the error remote host is not trusted. When I select the error to find out more it states "The remote host is not trusted. This could indicate P-AV-Transport header does not contain th. I can't find anything on that error though.
 
Upvote 0 Downvote
Are you using procr for connect to SM? What about network connectivity between ACM and SM? Can you make a telnet to SM on port 5060 from your ACM?
Are you sure that using correct IP address of SM in your siggrp? SM has two address: Management and SIP. You must use SIP.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

kozlik
  • Question
Session Manager "cust account expired"
Replies
2
Views
226
phoneguy55
phoneguy55
phoneguy55
  • Locked
  • Question
Session Manager Identity Certificates
Replies
3
Views
464
kyle555
kyle555
George FA
  • Locked
  • Question
traceSM shows no TLS traffic between CM and SM
Replies
0
Views
305
George FA
George FA
hebegb41
  • Locked
  • Question
Avaya SM/CM 8.1 J139 SIP phones and "bridged Appearances"
Replies
4
Views
910
hebegb41
hebegb41
George FA
  • Locked
  • Question
CM sends to SM SIP/2.0 403 Forbidden (TLS Required)
Replies
1
Views
493
George FA
George FA

Part and Inventory Search

Sponsor

Back
Top