More details: - a.conf
group=smsc smsc=smpp smsc-id=gprs-bill interface-version=34 host=10.1.7.21 port=1600 system-id=a smsc-password=a system-type=a transceiver-mode=true - b.conf group=smsc smsc=smpp smsc-id=gprs-bill interface-version=34 host=10.1.7.21 port=1600 system-id=b smsc-password=b system-type=b transceiver-mode=true So, starting to bearerboxes (normally with different ports) may cause any problem if both conf files have same smsc-id? Thanks On Wed, Nov 4, 2009 at 5:43 PM, vijay shanker <vijay.s...@gmail.com> wrote: > Can not be conformed. > > How many connection your SMMP service provider supports? > > Two bearer box may be running but on different ports. Try to find out or > give more relevant details. > > Like what is your configuration? or what is the problem you have > encountered. > > Regards, > Vijay Shanker Dubey > > > > > On Wed, Nov 4, 2009 at 9:22 PM, Elton Hoxha <elt...@gmail.com> wrote: > >> Hi guys, >> >> Is there any possibility to have conflict between two bearerbox processes >> running in paralel, having separate smpp connection but same SMSC name?? >> example: gprs-bill >> >> 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP[gprs-bill]: Sending enquire >> link: >> 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP PDU 0x9743758 dump: >> 2009-11-04 16:50:44 [5057] [6] DEBUG: type_name: enquire_link >> 2009-11-04 16:50:44 [5057] [6] DEBUG: command_id: 21 = 0x00000015 >> 2009-11-04 16:50:44 [5057] [6] DEBUG: command_status: 0 = 0x00000000 >> 2009-11-04 16:50:44 [5057] [6] DEBUG: sequence_number: 28 = 0x0000001c >> 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP PDU dump ends. >> >> I`m just doubting because I had some "connection reset" errors. >> >> Thanks >> > >
