" /> Route a call to a mobile phone - Genesys CTI User Forum

Author Topic: Route a call to a mobile phone  (Read 5961 times)

Ritchie

  • Guest
Route a call to a mobile phone
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Does anyone have ideas on how to use URS to route a call to an external number ie mobile phone?

Vic

  • Guest
Route a call to a mobile phone
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • That should be pretty simple just have URS place a call to it!
    All you need to do is defne the number in singlequote paranthesis and you are set. We had a client who wanted to place outbound calls with URS on Nortel and we set him up in less then two days.

    I think pretty soon someone should think about creating an outbound dialer using URS only! Of course, we will need a physical call coming from somewhere, but I am sure there is a way we can combine URS with Custom Server to control Dialogic card, or even PBX itself.

    John Doe

    • Guest
    Route a call to a mobile phone
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Do you want to route to the same number each time or to a variable? both methods are similar by using the TRoute function in IRD. If the number is fixed enter it as the 'destination', set the Route type to RouteTypeUnknown. If the number changes define the number you want to call as a variable earlier in the strategy, then, in the destination field click on the variable name (will be part of a drop down menu).

    Hope this helps

    Ritchie

    • Guest
    Route a call to a mobile phone
    « Reply #3 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Thx guys I have tried that already but it won't dial the number.
    Here is some of my ts log:



    @20:05:06.4177 [0] 6.5.202 distribute_event: message EventRouteRequest
    AttributeTimeinuSecs 417717
    AttributeTimeinSecs 1052334306 (20:05:06)
    AttributeOtherQueue '4002'
    AttributeThisQueue '4002'
    AttributeOtherDNRole 1
    AttributeOtherDN '8139'
    AttributeThisDNRole 2
    AttributeThisDN '4002'
    AttributeDNIS '4002'
    AttributeConnID 000000f9631c5fab
    AttributeCallID 2331
    AttributeCallType 1


    @20:05:06.4210 [0] Received from 13 (0003 urs_6510700): message RequestRouteCall
    AttributeThisDN '4002'
    AttributeConnID 000000f9631c5fab
    AttributeOtherDN '907710468183'
    AttributeExtensions [27] 00 01 00 00..
    'CUSTOMER_ID' 'Resources'
    AttributeRouteType RouteTypeUnknown
    AttributeReferenceID 26457
    TESTLV2: ts>route[CRV=1 <=> CRV=58]>link[1]
    ** ts6.5.202[1] ** 20:05:06.4213
    08 00 00 22 08 02 80 58 62 96 1C 1A 91 A1 17 02 01 64 02 01 B7 40 0F 70 0D 80 39 30 37 37 31 30 34 36 38 31 38 33
    === parsed message ===
    prot_discr = 8
    CRV = 8058
    MsgType = 98 (FACILITY)

    Facility: serv_discr = 17(q932_suppl) fac_ie = component_tag = A1(INVOKE)
    invoke_id tag: 02, value = 100
    operation tag: 02, value = 183(RouteSelect)
    params = q931_tag = 40
    list =
    Called_Party_Number: type_plan = 0(unknown) address = 907710468183


    ** link[1] ** 20:05:06.4701
    08 02 00 58 5A 96 1C 0F 91 A1 0C 02 01 01 02 01 B9 40 04 08 02 81 9C
    === parsed message ===
    prot_discr = 8
    CRV = 58
    MsgType = 90 (RELEASE COMPLETE)

    Facility: serv_discr = 17(q932_suppl) fac_ie = component_tag = A1(INVOKE)
    invoke_id tag: 02, value = 1
    operation tag: 02, value = 185(RouteEnd)
    params = q931_tag = 40
    list =
    Cause: code_std_loc = 1(CCITT_PubNetLocUsr) cause = 28(C_INVLDNUM C_COV_DONT_ANS)

    TESTLV2: link[1]>routeCRV[0x0058 <=> 0x0001]>ts
    @20:05:06.4706 [0] 6.5.202 distribute_response: message EventRouteUsed
    AttributeTimeinuSecs 470667
    AttributeTimeinSecs 1052334306 (20:05:06)
    AttributeReferenceID 26457
    AttributeCallState 3
    AttributeOtherQueue '4002'
    AttributeThisQueue '4002'
    AttributeThirdPartyDNRole 2
    AttributeThirdPartyDN '907710468183'
    AttributeOtherDNRole 1
    AttributeOtherDN '8139'
    AttributeThisDNRole 2
    AttributeThisDN '4002'
    AttributeExtensions [18] 00 01 01 00..
    'G3Cause' 600
    AttributeDNIS '4002'
    AttributeConnID 000000f9631c5fab
    AttributeCallID 2331
    AttributeCallType 1
    Wed May 07 20:05:06 2003.471 Trace donald LucentG3 GCTI04542 Message EventRouteUsed sent to 13 ( regular urs_6510700 )
    sent to 13 (0003 urs_6510700)
    Wed May 07 20:05:06 2003.471 Trace donald LucentG3 GCTI04542 Message EventRouteUsed sent to 16 ( regular statserver_cca )
    sent to 16 (0bf6 statserver_cca)
    Wed May 07 20:05:06 2003.471 Trace donald LucentG3 GCTI04542 Message EventRouteUsed sent to 15 ( regular statserver_main )
    sent to 15 (05c7 statserver_main)
    PARTIES:
    Call_info: call_id 2331, conn_id 000000f9631c5fab, assoc 0xec7 Internal
    VDN=4002 routed_to=907710468183
    1) 8139, role 1, state OH+(Dialing), id=1, Created:1052334304
    2) 4002(queue), role 2, state QS+(RouteUsed), queue=4002, Created:1052334304


    TESTLV2: Party found: party_id = 1, DN = 8139
    @20:05:06.4740 [0] 6.5.202 distribute_event: message EventReleased
    AttributeTimeinuSecs 474012
    AttributeTimeinSecs 1052334306 (20:05:06)
    AttributeCallState 0
    AttributeOtherQueue '4002'
    AttributeOtherDNRole 2
    AttributeOtherDN '4002'
    AttributeThisDNRole 1
    AttributeThisDN '8139'
    AttributeDNIS '4002'
    AttributeConnID 000000f9631c5fab
    AttributeCallID 2331
    AttributeCallType

    PARTIES:
    Call_info: call_id 2331, conn_id 000000f9631c5fab, assoc 0xec7 Internal
    VDN=4002 routed_to=907710468183
    1) 8139, role 1, state DELETED+OH+(Released), id=1, Created:1052334304
    2) 4002(queue), role 2, state QS+(RouteUsed), queue=4002, Created:1052334304

    ED

    • Guest
    Route a call to a mobile phone
    « Reply #4 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Can you dial that number exactly from a physical set? ( on the same side of the PBX as Genesys)

    Ritchie

    • Guest
    Route a call to a mobile phone
    « Reply #5 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • It's cool it was the COR on the switch for the RP I was using. Damn switch guys told me everything was ok with the COR. Always check yourself is the rule I think!

    Thx for the advice though.