SIP trunking between SubFinder and Avaya Aura Communication Manager 1

[wyzemagi]

Has anyone ever tried setting up a SIP trunk between CM and a product called SubFinder? I have one setup but the trunk group status shows out of service/ far end. To me that means SubFinder doesn't see the SIP trunk. In CM I have a signaling group set with the procr as the near end and the SubFinder the far end via node-names. I also have DTMF set to in-band (per the vender requirements). Codec is set to g711MU. Transport method is TCP and port 5060 though vednor is asking for UDP. The Signaling group doesn't offer that option though. Only TCP or TLS. I then have a DID pointing to that TG. Inbound calls do reach the TG but I get a busy single because the trunk is OOS/FE. I have plenty of SIP trunk licenses in CM.

On the SubFinder side there seems to be only one setting. In the INI file for the call processor app you can put the IP of the SIP gateway (that would be the CM in this case). That's it. The only other thing I can see to set are the dial patterns. The vendor states that SIP is the only option for this product. It is a virtual machine in the customer's network. I made sure to turn off any firewalls in the VM. Are there any other settings in SubFinder that I have not found to get the SIP trunk in service?

 

[kyle555]

Session Manager would be your friend. I don't think CM does UDP SIP signaling. Depending how enterprise-y you want to get, maybe an Audiocodes or similar SIP gateway could do that for you, or, if you're on the cheap, a back to back SIP proxy to talk TCP to CM and UDP to your app.

http://siproxd.sourceforge.net/

 

[wyzemagi]

I like your thinking Kyle555. I do actually have a Session Manager in place as well. I've setup the SubFinder as an entity link with UDP 5060. The connection and link status are both ok/up. SubFinder outbound calls are dropped immediately. Inbound calls do reach SubFinder now. That's more than when I had a direct CM SIP trunk. I was thinking it might be a problem with DTMF or hostname issues on the SIP link coming from SubFinder back to SM. I am also hoping an adaptation might help. Do you agree or am I going about this all wrong? If so, any wisdom on how to setup the adaptation properly for ingress (technically it would be considered an inbound call by the SM I think)? Thanks! I'll take a look at your link in the meantime.

 

[kyle555]

Nope, you seem to be doing it all right.

traceSM from the CLI of Session Manager will let you do a SIP trace and call processing trace - to see what it is about your Invites and how they flow through SM to not get out.

You might want to set your default SIP domain for UDP port 5060 on the SIP Entity to SubFinder. Confirm that sip domain is authoritative for the network region and on the signaling group form in CM. And you'd just want to make sure whatever digits it would dial to get to CM have the relevant dial patterns in SM with a routing policy. Something like "If i get 9999 from SubFinder on UDP port 5060, it will be for domain wyzemagi.com, it will match the dial pattern of 9 min/max 4 digits, and take the routing policy that uses my CM as the destination SIP entity

 

[wyzemagi]

Thanks Kyle555! I have the default domain set. It is authoritative for net reg and sig group. Sounds like my dial/route patterns need to be tweaked. I'll confirm with traceSM.