Those two are identical, you could remove one of them and you'll be fine (of course it'll be reported with the same name on both smsc's but it'll work as you expect). You'd get into trouble if the configuration would be different (e.g., one integer, one nulterminated). I'm not sure which one would be honored or if you'd get a panic, why don't you give it a shot? ;)
Regards, Alejandro On Fri, Aug 7, 2009 at 6:00 PM, Marcelo Olivas <[email protected] > wrote: > Guys, out of curiosity, if I have a two TLVs configured for two different > SMSC and one of the address is shared by them, would we get an error or > would it take the last one? > For example: > > group = smpp-tlv > name = tlv_a > tag = 0x1601 > type = octetstring > length = 20 > > group = smpp-tlv > name = tlv_b > tag = 0x1601 > type = octetstring > length = 20 > > On Aug 7, 2009, at 11:51 AM, Alejandro Guerrieri wrote: > > Yeah, definitely a place for improvement, specially since everybody just > "loves" 0x140X addresses ;) > Regards, > > Alejandro > 2009/8/7 Nikos Balkanas <[email protected]> > >> Hmmm, in other words there is no way to bind the tlv group to a specific >> smpp instance. In such cases I only check gwlib/cfg.def. There is support >> for smsc-id there, therefore it looks it was intended to be implemented. >> >> Maybe time for a meta-patch? >> >> BR, >> Nikos >> >> ----- Original Message ----- >> *From:* Alejandro Guerrieri <[email protected]> >> *To:* Users mailing list <[email protected]> >> *Sent:* Friday, August 07, 2009 5:25 PM >> *Subject:* Re: How to bind smpp-tlv to a specific smsc group >> >> I wrote the documentation for the meta-data functionality and of course >> I'vechecked the code at that moment to figure out the inner details of it's >> functionality. >> >> I've just re-checked the code and, while there's an entry for the smsc-id >> as a valid parameter on the smpp-tlv group, I didn't found any place on the >> code where this parameter is read an used when binding the TLV definitions. >> >> Please check on gw/smsc/smpp_pdu.c around line 108, it reads "name", >> "tag", "length" and "type", but not "smsc-id". >> >> In short: while you'd be able to put "smsc-id" on your "smpp-tlv" group, >> it'll be ignored. >> >> Regards, >> >> Alejandro >> >> 2009/8/7 Nikos Balkanas <[email protected]> >> >>> Hi, >>> >>> This is a straightforward one. I am surprised it is not in the user >>> guide. Just add in the smpp-tlv group: >>> >>> smsc-id = <smscID> >>> >>> You need to have defined <smscID> beforehand in your smsc definition. >>> >>> BR, >>> Nikos >>> ----- Original Message ----- From: "Rolandow" <[email protected]> >>> To: <[email protected]> >>> Sent: Friday, August 07, 2009 12:56 PM >>> Subject: How to bind smpp-tlv to a specific smsc group >>> >>> >>> >>> Hi all, >>>> >>>> I need to start working with the smpp-tlv mechanism as supported in the >>>> latest release of Kannel. I read the snapshot userguid, and there was a >>>> briefly description how to implement this. >>>> >>>> From the manual I found: >>>> >>>> group = smpp-tlv >>>> name = my_tlv_name >>>> tag = 0x1601 >>>> type = octetstring >>>> length = 20 >>>> >>>> This sounds very clear, but how does Kannel know for which smsc group >>>> this extra TLV is? I have several connections on my Kannel installation, so >>>> I think I need to specify somehow which SMSC is using extra TLV's? >>>> >>>> How can I do this? >>>> >>>> Thanks in advance! >>>> >>>> Kind regards, >>>> Roland. >>>> >>>> >>> >>> >> > >
