CTJackal

Member

Last active 14 years ago

  1. 14 years ago
    Sat Feb 13 13:03:51 2010
    CTJackal posted in SQL query for incoming calls.

    Thnaks for you quick response Nicolas. I've set up one of the incoming DDIs to go straight to a single extension (500) and I've done as you suggest re: debugging mode, and the line I suspect I should be looking at is:

    127.0.0.1 <- Event: AGIExec
    127.0.0.1 <- Privilege: call,all
    127.0.0.1 <- SubEvent: End
    127.0.0.1 <- Channel: SIP/87.xxx.xxx.242-09e92118
    127.0.0.1 <- CommandId: 1478964973
    127.0.0.1 <- Command: VERBOSE "Caller ID name is 'Main Number - Xxxx Xxxxxxxx Xxxxxxx' number is '017xxxxxx00'" 1
    127.0.0.1 <- ResultCode: 200
    127.0.0.1 <- Result: Success
    127.0.0.1 <- Server: 0

    I've blanked out the personal data with xxxx in the above.

    I assume that Asterisk is passing the info through. I have set up Asterisk to use a different SQL database, hence it recognises the name associated with the caller ID.

    What should I be looking for if not the above section?

    Cheers,
    Carlos.

  2. Wed Feb 10 14:38:54 2010
    CTJackal started the conversation SQL query for incoming calls.

    Hi, I seem to have managed to get the Phonebook working, but any incoming calls are simply displaying the extension or ring group rather than the incoming CID.

    For example:

    DID: 01432765098
    Incoming CID: 01234567890
    Inbound rules : 01432765098 -> Ring Group 700
    Ring Group 700: Ext 500 & Ext 501

    The FOP2 screen shows an incoming call, but it appears to come from Ext 700, so nothing is returned from the SQL query.
    When I checked the SQL query, it reads:

    SELECT concat(firstname,' ',lastname,'<br/>',company) as name,picture FROM visual_phonebook WHERE phone1 LIKE '%500'OR phone2 LIKE '%500' LIMIT 1

    For some reason FOP2 seems to be picking up the called ring group as the CID. Any iseas how to correct this to show the actual CID?

    Carlos.