SIP trunking directly to Intercall

[f0netech]

We are working on a project with Intercall so that our offices can place SIP-to-SIP calls to save on the expense of utilizing public networks. All of the networking pieces are configured and we know that we have the appropriate paths to reach their network. The final piece was putting together a SIP-to-SIP tie line and routing the calls utilizing separate SIP trunk. We have pieced together the Signaling group, Network region and SIP trunk by replicating what we use when placing calls over our Sprint network. Everything shows IN-Service, but when we place calls over the trunk it eventually fails and we hear fast busy. When running a trace, the denial event is 1191 which seems to be to be a generic 'network fail'. Any suggestions from the group would be appreciated?

SIGNALING GROUP

Group Number: 80 Group Type: sip
Transport Method: tcp
IMS Enabled? y





Near-end Node Name: Clan-01b03 Far-end Node Name: Intercall
Near-end Listen Port: 5060 Far-end Listen Port: 5060
Far-end Network Region: 230
Far-end Domain:

Bypass If IP Threshold Exceeded? n
Incoming Dialog Loopbacks: eliminate RFC 3389 Comfort Noise? n
DTMF over IP: rtp-payload Direct IP-IP Audio Connections? y
Session Establishment Timer(min): 3 IP Audio Hairpinning? y
Enable Layer 3 Test? n Direct IP-IP Early Media? n
H.323 Station Outgoing Direct Media? n Alternate Route Timer(sec): 30

TRUNK GROUP

Group Number: 800 Group Type: sip CDR Reports: y
Group Name: InterCall COR: 1 TN: 1 TAC: 8334
Direction: two-way Outgoing Display? n
Dial Access? n Night Service:
Queue Length: 0
Service Type: tie Auth Code? n

Signaling Group: 80
Number of Members: 20
Group Type: sip

TRUNK PARAMETERS

Unicode Name: yes

Redirect On OPTIM Failure: 32000

SCCAN? n Digital Loss Group: 18
Preferred Minimum Session Refresh Interval(sec): 600

 

[montyzummer]

Couple of things , need to see a list trace tac/s or list trace station/s the /s will provide in depth sip messaging in the trace output.

Also need to see your route pattern and public unknown numbering config.

Also what protocols are in use a , b or c on the sig and trunk group.

In essence this is a simple set up and im sure with a list trace output and a full config posting instead of parts bits we can get you there.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[mattKnight]

hmmmm

does Far-end Node Name: Intercall

resolve to same place?

AFAIK, intercall are a SIP trunking supplier. What you seem to be doing is expecting the intercall SIP network to act like a MPLS cloud...

IF intercall allow free calls between intercall subscribers, you still need to treat this like a PSTN type call. Are you?



Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[f0netech]

Thank you for the response all.

Later in the day we were able to resolve the matter. In lieu of having the Signaling group / Tie line scenario, we were able to conclude that a Mapping entry in our SES specific to the Intercall calling number needed to be entered. We are still traversing the call(s) over a separate route pattern so that we could transmit different digits to Intercall, but all is working now.

Thanks again.