SMSC name conflict???

2009-11-04 Thread Elton Hoxha
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

Fwd: SMSC name conflict???

2009-11-04 Thread Elton Hoxha
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

Re: SMSC name conflict???

2009-11-04 Thread Alvaro Cornejo
Elton I think it is more a problem from your SMSC provider. If they do allow you to have 2 -or more- connections to the same port or not. The connection resets can happen for multiple reasons including problems on any of the peers, the network (Lan/Wan) , etc. Hope helps

Re: SMSC name conflict???

2009-11-04 Thread Elton Hoxha
Thanks Alvaro but its a misundesrtanding. ITs not a matter of SMSC provider. Im just thinking from kannel point of view, considering the example I gave above. Actually both conenctions are live and running, but sometimes having interruption, connection reset by peer. When sending the enquiry link,

Re: SMSC name conflict???

2009-11-04 Thread Nikos Balkanas
:30 PM Subject: Re: SMSC name conflict??? Thanks Alvaro but its a misundesrtanding. ITs not a matter of SMSC provider. Im just thinking from kannel point of view, considering the example I gave above. Actually both conenctions are live and running, but sometimes having interruption