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!

Transfer over SCN to IPOCC Topic

Status
Not open for further replies.

davea2

Technical User
Mar 14, 2005
742
GB
Hi

I am trying to transfer calls (manually) over an SCN to another site to ring in the IPOCC contact centre.
They dial a short code (666, their choice ;) ) which the feature is dial and the telephone number is the topic shortcode on the IPOCC system.
The outgoing trunk is the outgoing group of the SCN line.

We just get busy and the call is dropped.

One thing I noticed on the monitor trace at the IPOCC end is "Detected Redirect IPOCC loopback"

Trace below

Any ideas??

Thanks!

77078939mS CMTARGET: 0a01610100001285 241.1064.1 678 ShellyHuntley.0: ~CMTargetHandler f4eae824 ep f16c9c94
77080693mS CMTARGET: 0a015f0200000006 17.15.1 679 H323TrunkEP: LOOKUP CALL ROUTE: GID=0 type=100 called_party=6115 sub= calling= calling_sub= dir=out complete=1 ses=0
77080693mS CMTARGET: 0a015f0200000006 17.15.1 679 H323TrunkEP: ADD TARGET (N): number=6115 type=100 depth=1 nobar=1 setorig=1 ses=0
77080694mS CMTARGET: 0a015f0200000006 17.15.1 679 H323TrunkEP: SYS SC: 6115 4 15 sc=type=DialExtn code=61XX, num=400|>>. callinfop->sending_complete=1 secondary_dialtone=
77080695mS CMTARGET: 0a015f0200000006 17.15.1 679 H323TrunkEP: ADD TARGET (N): number=400 type=100 depth=2 nobar=1 setorig=1 ses=0
77080695mS CMTARGET: 0a015f0200000006 17.15.1 679 H323TrunkEP: SET USER: SipUser orig=1
77080695mS CMTARGET: 0a015f0200000006 17.15.1 679 H323TrunkEP: ADD USER: SipUser depth=2 disallow_cw=0 dnd=0 real_call=1 group_call=0 type(CMNTypeDefault) incl(0x0) excpt(0x0), allow_redir(1) remote=00000000 simult 0 (0)
77080697mS CMTARGET: 0a0161010000128b 251.4747.0 679 SipUser.0: ADD PRIMARY
77080698mS CMTARGET: 0a015f0200000006 17.15.1 679 H323TrunkEP: INITIAL TARGETING SUCCEEDED
77080698mS CMTARGET: 0a015f0200000006 17.15.1 679 H323TrunkEP: Detected Redirect IPOCC loopback. Re-target from (0a015f0200000006 17.15.1 679 H323TrunkEP)
77080703mS CMTARGET: 0a015f0200000006 17.15.1 -1 BaseEP: ~CMTargetHandler f4eae824 ep f163fdcc

 
It doesn't show calling party.

What is the exact call scenario here?

Incoming call on xxx trunk etc?

"Trying is the first step to failure..." - Homer
 
I have tried getting a user on the non-IPOCC site to dial 666

Also, to avoid bothering them constantly, I set up a DDI on an ISDN with destination of 666 (shortcode to dial 6115 up the SCN to the IPOCC site)
(That is the scenario in the above trace)

400 is the SIP extension to the IPOCC

Both scenarios give busy

Clearly the 6115 is recognised correctly as a shortcode on the IPOCC IPO (SYS SC: 6115 4 15 sc=type=DialExtn code=61XX, num=400|>>.)
So I am totally stumped as to why it gets rejected by the IPOCC
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top