HMC
Product Manual
163
Release 3.4: May 2010
Console Suite
4.
The HG matches the originating user (CLI and/or PIN Code) to the predefined registered
user.
5.
After HG assumes a correct user authentication, the HG redials to the registered user.
This is indicated by: MGWCallback (0) Leg1 event [DialAck.
6.
After the User answers, the HG plays a dial tone. This is indicated by: playDialTone.
7.
The User can dial the desired destination called party by sending each digit of the destina-
tion called party number using DTMF: 0774445016.
8.
When one party hangs-up the call, the HG starts to Close Resources and removes media
resources.
SMS Callback Log
Following are excerpts from a SMS Callback Log.
[26/03-10:39:40.805] HMCServer received [ping] from 127.0.0.1/127.0.0.1:4043
…
SMSRawCallback /A24/z/I1050/r1/N"+972544331123"/i0/G"0774445016"
…
[26/03-10:39:44.391]
Adding message [SMSRawCallback
/A24/z/I1050/r1/N"+972544331123"/i0/
G"0774445016"] to eventQueue for Client -1 Application ID 0
…
[26/03-10:39:47.459]
Creating session: Code=[0602], UserId=[udi2], AccessNum
=[], EventSource=[/tSMS/
A24/r1]
…
[26/03-10:39:47.680]
MGWCallback (4) Leg1 event [DialAck
/A24/I4/o1]
…
[26/03-10:39:59.131]
MGWCallback (4) Leg2 event [DialAck /A24/I5/o1]
…
[26/03-10:40:44.917] * Received Packet: Ack /A2b/x0,1/I32
Explanation
SMS Callback works as follows. SIM 1 is defined to ‘listen’ for an incoming SMS from a reg-
istered user. SIM 2 is defined as LEG 1 and calls back the registered user and cross-connects
with SIM 3. SIM 3 is defined as LEG 2 and calls to the destination party and cross connects
with SIM 2.
1.
In this case the registered user 0544331123 is sending an SMS message to the number of
SIM1. The SMS message contains the destination number.
2.
The HG receives the SMS and starting its SMS callback engine. This is indicated by:
Adding message [SMSRawCallback . . .