IPO Forwarding Caller id "restricted"

[turbo2ltr]

Hoping you wonderful people can give me a clue..

I have an IPO 500 with a sip trunk to an Asterisk server.
IPO has an auto attendant, "press 1 for sales". That destinates to a ring group. Works fine.

My task was to forward sales calls between 5 and 7 to our west coast office (the asterisk server)

I tried it a bunch of ways but in every instance, the caller id of the forwarded call to the west coast came up "restricted". This is not an issue when an IPO extension directly dials an asterisk extension. It only seems to be an issue if there is an auto-attendant somewhere along the route. Also keep in mind that the "internal" sip trunk between the IPO and the Asterisk is not subject to call ID "hardcoding" like the external SIP trunk we use for regular outgoing calls so it should go through.

The current setup is:

Incoming -> AA -> [press 1] -> Sales Hunt Group set up for night service failover between 5 and 7 -> West Coast Hunt Group -> Ext 253 -> Forward unconditionally to 6701 (west coast ext)

If in the AA I dial 253 directly instead of 1, it calls the west coast with the ext 253 caller id. If I hit 1 I get restricted.

I assume I'm missing something stupid.

I've tried using a short code with ss at the end as a forwarding number (as suggested in another thread), but that didn't work either. The short code forced the use of the internal sip trunk.

Any ideas would be most appreciated. I would love to get the originating caller ID to come through the Asterisk. Or the very least extension 253 so we know its a east coast call.

Thanks!

 

[kyle555]

What release are you on?

I know in the SIP line on 9.1, "send caller ID" can be either diversion header, PAI, or Remote Party ID and there's a lot of options in the the "SIP Advanced" tab.

Have you done a SIP monitor trace or a PCAP to see if IPO is sending the originating number somewhere in the SIP messaging?

 

[turbo2ltr]

IP500 V2
Firmware 7.0 (32)

I haven't done a sip trace, mostly because I know the IPO can send at least the IPO extension number to the forwarding number as demonstrated when dialing the extension directly. But I'm not even getting that. I figured once I got that I can move on to trying to get the external number to come through to the west coast.

I did a sip trace.. 100.30 is the asterisk server, 1.50 is the IPO. 701 is the asterisk hunt group extension.

[pre]
<--- SIP read from UDP:xxx.xxx.1.50:5060 --->
INVITE sip:701@xxx.xxx.100.30 SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.1.50:5060;rport;branch=ad25f3899a1ad25f385a99a40ad25f38fef3efd5
From: "Anonymous" <sip:restricted@[asteriskserver].com>;tag=d7aad25f388de39
To: <sip:701@xxx.xxx.100.30>
[/pre]

 

[intrigrant]

Try this:

In the IP Office SIP URI fill in a * for PAI.
Create a shortcode like *99N;\NSS\Call\SIP Line ID, set the forward number as *99<target number>

 

[turbo2ltr]

Thanks for the info. Unfortunately it didn't do anything.

Ext 253 forwards to *601
*601 is set up Dial/701SS;/Asterisk trunk line group

701 is the west coast sales ring group on the asterisk server.



ok I see what is causing some confusion on my side... My asterisk extension at my desk (the one I'm making the test calls on) is 251 and the IPO is doing a CID lookup and returning *its* ext 251 name even though the numebr is 253. So I switched phones (all other west coast asterisk extensions are in the 100s) and came up with this:


Dialed direct via the asterisk system from ext 108:
Ext 253 (the one that forwards) - CID: ext 253 name of 253
HG 292 (hunt group that rings 253) - CID: Ext 292, no name

Dialed through the east coast DID and into AA:
Ext 253 (the one that forwards) - CID: 253, ext 253 name of 253
HG 292 (hunt group that rings 253) - CID: Restricted
1 for sales (Fwds to HG 290 which rings a bunch of IPO ext) - CID (on IPO ext): DID of west coast asterisk system (confirm it's not the asterisk system holding the CID back)

I tried changing the "send callerid" setting in the asterisk sip trunk setting (diversion Header, P asserted, Remote Party) but none of the settings made a difference. dialing 253 always forwarded with CID of 253 and dialing the HG 292 always returned restricted.

This is all with the PAI of the SIP URI set to *

 

[sizbut]

If the SIP line is set to use internal data, then the System | Voicemail tab includes options for how the identity should be set on SIP calls routed by the voicemail service.

Stuck in a never ending cycle of file copying.