Originating CLID is not shown when using mobile Twinning

[Jeffnortel]

Hello,

Would someone confirm if I'm reading the system monitor trace correctly? It appears the IPO is forwarding the originating CLID but the carrier may be blocking it. The call does complete but with the PRI BTN as the CLID. I used an analog extension for testing so a short code was used to make the twinned leg of the call.

Call scenario...
phone # 1112225849 calls 1112227010(extn 3314)
extn 3314 is mobile twinned to short code 2227295 (SC 2227295 - Dial - 1112227295
then the twinned leg of the call begins...

see attached monitor trace... Thanks!

 

[janni78]

Are you even allowed to send originating number on the PRI?

Normally this is not allowed and therefore you get the PRI main number instead.

You don't have ISDN L3 traces included so you don't see what is sent on the actual ISDN setup but it looks like it's sending the original number.

"Trying is the first step to failure..." - Homer

 

[Jeffnortel]

Yes sir, I'm 100% certain this can be done using a PRI. The carrier may need to allow but I wanted to be sure it wasn't the IPO first. The sys mon trace options are set to default values. What other selections are needed?

 

[derfloh]

ISDN Layer3 is needed. IPO is able to send the number but the carrier has to allow it. No need to test with IPO as long as it denied by the line provider.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[Jeffnortel]

Again, the ISDN L3 box was checked when I captured the call. System monitor default trace values are set this way...

I did not want to assume the carrier was blocking before I confirmed the IPO was working as expected. Typically I look at my part first before pointing the finger at others... Thanks anyway

 

[j.flanagan]

Maybe a dumb question, but under the system-twinning tab do you have checked "send original calling party for Mobil Twinning?