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!

Incomming SIP trunk to outgoing PRI Trunk

Status
Not open for further replies.

IPOCraft

Technical User
Apr 9, 2014
49
PE
Hi there:

I'm trying to establish a call from a Cisco to the PSTN via E1 connected to a IPO. The trunk between IPO and Cisco in a SIP trunk. I can communicate between the two nodes (Cisco-Avaya) via trunk setup and ICR. When Cisco calls IP Office extensions, they follow the ICR rules:

- Incomming Number: blank
- Trunk: 7 (The SIP trunk)
- Destination: .

I have a Short Code 9N to ARS:Main and I trying to call from Cisco to the PSTN dialing 9XXXXXX. I see in the Monitor the call in the SIP Trunk but IPO responds "Unallocated (unassigned) number".

I trying the following ICR without success:

- Incomming Number: 9XXXXXX
- Trunk: 7
- Destination: 9#

How can I setup the IPO to act like a passover between SIP to E1-PRI?
 
I am taking a guess, but since you are using trunks, you have to allow trunk to trunk transfer and/or allow off site transfer. You might be restricted.
 
The ARS for the cisco would need to insert a 9, so create an ARS just for the cisco that inserts the 9. So for long distance the ARS would have 91N and local would use 9N. Worth a shot.
 
Trunk to Trunk transfer is allowed. Cisco is sending 9 + Phone Number (96154300), but is not matching with the ARS 9N code:

76613476mS SIP Tx: UDP 192.168.0.3:5060 -> 192.168.0.254:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.254:5060;branch=z9hG4bK9615BC
From: "IPCOMM" <sip:8720@192.168.0.254>;tag=49F3688-A13
Call-ID: 2F382DB-765B11E9-85BD95BC-7341762B@192.168.0.254
CSeq: 101 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 9.0.6.0 build 979
To: <sip:[highlight #FCE94F]96154300[/highlight]@192.168.0.3>;tag=8a3ee36050809af9
Content-Length: 0

[highlight #729FCF]76613478mS Sip: 18.1991.1 -1 SIPTrunk Endpoint(f4be3c28) Present Call, no match (96154300) from URI in To header or (96154300) from request URI[/highlight]
76613478mS Sip: SIPTrunkEndpointDialogOwner::SetRemoteAddressForResponse from 192.168.0.254:5060 to 192.168.0.254:5060
76613479mS SIP Tx: UDP 192.168.0.3:5060 -> 192.168.0.254:5060
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.0.254:5060;branch=z9hG4bK9615BC
From: "IPCOMM" <sip:8720@192.168.0.254>;tag=49F3688-A13
Call-ID: 2F382DB-765B11E9-85BD95BC-7341762B@192.168.0.254
CSeq: 101 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 9.0.6.0 build 979
Reason: Q.850;cause=1;text="[highlight #EF2929]Unallocated (unassigned) number[/highlight]"
To: <sip:96154300@192.168.0.3>;tag=8a3ee36050809af9
Content-Length: 0

It's like is searching the 96154300 extension in the IPO!
 
My guess is the outbound callerid. If it is sending a callerid that the pri does not like, it will reject. You will probably have to force the outbound callerid.

 
Now it's working. It needs an "*" in the Local URI field, in the URI SIP Tab of the SIP Trunk to follow the ICR rules. Otherwise it will treat the "To: Field" in the SIP messaging as an possible extension.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top