Hi,

I am sorry, this is not what I was looking for. "bb" is shorthand for 
bearerbox. The SMSC PDU should be there. If you could note the operator-id from 
there.

Thanks,
Nikos
  ----- Original Message ----- 
  From: Karan Zaveri 
  To: 'Nikos Balkanas' 
  Cc: [email protected] 
  Sent: Sunday, September 27, 2009 4:27 PM
  Subject: RE: Incorrect Operator ID returned


  Hmm that might be a bit tough because the PDU shown by the SMSbox is in 
numbers and at the end
  where the data is the operator_id shows blank but here’s the sample

   

  2009-09-26 08:18:47 [32638] [9] DEBUG: HTTP: Opening connection to 
`www.instadiumsolutions.com:80' (fd=28).

  2009-09-26 08:18:47 [32638] [9] DEBUG: Socket connecting

  2009-09-26 08:18:47 [32638] [8] DEBUG: Get info about connecting socket

  2009-09-26 08:18:47 [32638] [8] DEBUG: HTTP: Sending request:

  2009-09-26 08:18:47 [32638] [8] DEBUG: Octet string at 0x698720:

  2009-09-26 08:18:47 [32638] [8] DEBUG:   len:  255

  2009-09-26 08:18:47 [32638] [8] DEBUG:   size: 1024

  2009-09-26 08:18:47 [32638] [8] DEBUG:   immutable: 0

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 47 45 54 20 2f 73 74 61 67 69 
6e 67 5f 6e 65 77   GET /staging_new

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 2f 6d 74 5f 6d 65 73 73 61 67 
65 73 2e 70 68 70   /mt_messages.php

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 3f 73 6f 75 72 63 65 5f 6e 6f 
3d 31 39 35 34 32   ?source_no=19542

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 33 34 33 33 30 38 26 73 68 6f 
72 74 5f 6d 65 73   343308&short_mes

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 73 61 67 65 3d 43 6f 6e 74 65 
73 74 2b 53 74 65   sage=Contest+Ste

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 76 65 2b 25 43 32 25 41 31 2b 
38 25 33 41 31 38   ve+%C2%A1+8%3A18

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 41 4d 26 6f 70 65 72 61 74 6f 
72 5f 69 64 3d 26   AM&operator_id=&

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 72 65 63 65 69 76 65 72 3d 36 
39 30 35 30 26 74   receiver=69050&t

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 69 6d 65 3d 32 30 30 39 2d 30 
39 2d 32 36 2b 31   ime=2009-09-26+1

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 32 3a 31 38 3a 34 37 20 48 54 
54 50 2f 31 2e 31   2:18:47 HTTP/1.1

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 0d 0a 48 6f 73 74 3a 20 77 77 
77 2e 69 6e 73 74   ..Host: www.inst

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 61 64 69 75 6d 73 6f 6c 75 74 
69 6f 6e 73 2e 63   adiumsolutions.c

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 6f 6d 0d 0a 43 6f 6e 6e 65 63 
74 69 6f 6e 3a 20   om..Connection: 

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 6b 65 65 70 2d 61 6c 69 76 65 
0d 0a 55 73 65 72   keep-alive..User

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 2d 41 67 65 6e 74 3a 20 4b 61 
6e 6e 65 6c 2f 63   -Agent: Kannel/c

  2009-09-26 08:18:47 [32638] [8] DEBUG:   data: 76 73 2d 32 30 30 39 30 39 32 
30 0d 0a 0d 0a      vs-20090920....

  2009-09-26 08:18:47 [32638] [8] DEBUG: Octet string dump ends.

  2009-09-26 08:18:50 [32638] [8] DEBUG: HTTP: Status line: <HTTP/1.1 200 OK>

  2009-09-26 08:18:50 [32638] [8] DEBUG: HTTP: Received response:

  2009-09-26 08:18:50 [32638] [8] DEBUG: Octet string at 0x68e370:

  2009-09-26 08:18:50 [32638] [8] DEBUG:   len:  499

  2009-09-26 08:18:50 [32638] [8] DEBUG:   size: 1024

  2009-09-26 08:18:50 [32638] [8] DEBUG:   immutable: 0

   

  Do you think the operator is not sending it? I can check with them again.

   

  Thanks

  Karan

   

  From: Nikos Balkanas [mailto:[email protected]] 
  Sent: Sunday, September 27, 2009 9:03 AM
  To: Karan Zaveri
  Cc: [email protected]
  Subject: Re: Incorrect Operator ID returned

   

  Hi,

   

  Could you please post PDU returned from bb logs with operatorID in bold?

   

  Thanks,

  Nikos

    ----- Original Message ----- 

    From: Karan Zaveri 

    To: 'Alejandro Guerrieri' ; 'Nikos Balkanas' 

    Cc: [email protected] 

    Sent: Sunday, September 27, 2009 3:48 PM

    Subject: RE: Incorrect Operator ID returned

     

    Hi Guys,

     

    I think I found the piece of code that is responsible for creating this URL 
data. It’s in the gw/urltrans.c file
    line 495  

     

        case 'o':  /* account information (may be operator id for aggregators */

            if (octstr_len(request->sms.account)) {

                enc = octstr_duplicate(request->sms.account);

                octstr_url_encode(enc);

                octstr_append(result, enc);

                octstr_destroy(enc);

            }

            break;

     

    Clearly it is returning the account id I just need to find out where is the 
sms object initiated and if there
    was a way to access the other variables available with it. Please let me 
know if you are aware of it.

     

    Thanks

    Karan

     

    From: Alejandro Guerrieri [mailto:[email protected]] 
    Sent: Sunday, September 27, 2009 6:34 AM
    To: Nikos Balkanas
    Cc: Karan Zaveri; [email protected]
    Subject: Re: Incorrect Operator ID returned

     

    According with the configuration file he posted on his first message, he 
does...

    Regards,

     

    Alejandro

    2009/9/27 Nikos Balkanas <[email protected]>

    Of course you need to have SMPP SMSc for that to work :-)

     

    NIkos

      ----- Original Message ----- 

      From: Alejandro Guerrieri 

      To: Karan Zaveri 

      Cc: Nikos Balkanas ; [email protected] 

      Sent: Saturday, September 26, 2009 9:54 PM

      Subject: Re: Incorrect Operator ID returned

       

      You're using an aggregator right? Maybe they use a TLV to send you the 
carrier id? Check the documentation or ask your SMSC provider about it. 

       

      Regards,

       

      Alejandro

      On Sat, Sep 26, 2009 at 7:13 PM, Karan Zaveri <[email protected]> wrote:

      Thanks Nikos,

       

      I tried that but it didn’t work. What I really need is the message 
sender’s Operator’s ID which is a number
      identifying who the operator is like Sprint = 31005, Cingular = 31002  
etc. The %o returns the system-type
      variable from the config file and the %i returns the SMPP hostname which 
is not what I am looking for.

      I am not sure if this is a bug in Kannel or some other setting that I 
need to do.

       

      Appreciate your help.

       

      Thanks

      Karan

       

      From: Nikos Balkanas [mailto:[email protected]] 
      Sent: Saturday, September 26, 2009 11:50 AM
      To: Karan Zaveri; [email protected]
      Subject: Re: Incorrect Operator ID returned

       

      Hi,

       

      Try %i to get the smsc-id.

       

      BR,

      Nikos

        ----- Original Message ----- 

        From: Karan Zaveri 

        To: [email protected] 

        Sent: Saturday, September 26, 2009 4:12 PM

        Subject: Incorrect Operator ID returned

         

        Hi All,

         

        I have been trying to integrate Kannel with our SMS application and so 
far have had success receiving
        messages however, I am having a bit of hard time trying to get Kannel 
return the operator id of the message.

        Based on the documentation I set the %o value in the response URL but 
instead of sending a numeric operator
        ID Kannel returns the smsc-username value. I am not sure if there is 
any additional setting that would need
        to be done in order to get the original operator id of the sender. Any 
help would be appreciated.

         

        Attached is my config file.

         

        Thanks

        Karan

      No virus found in this incoming message.
      Checked by AVG - www.avg.com
      Version: 8.5.409 / Virus Database: 270.13.112/2390 - Release Date: 
09/26/09 05:51:00

       

     

    No virus found in this incoming message.
    Checked by AVG - www.avg.com
    Version: 8.5.409 / Virus Database: 270.13.112/2390 - Release Date: 09/26/09 
05:51:00

  No virus found in this incoming message.
  Checked by AVG - www.avg.com
  Version: 8.5.409 / Virus Database: 270.13.112/2390 - Release Date: 09/26/09 
05:51:00

Reply via email to