symbian-port - unable to register

KB
Karthik Babu
Mon, Aug 25, 2008 5:10 PM

Hello Nanang ,

I have just noticed that the registration is failing and could not use the
app  using GPRS (tested on both  e61 and n95 ) .

Can you please advise ?

--
Karthik

Hello Nanang , I have just noticed that the registration is failing and could not use the app using GPRS (tested on both e61 and n95 ) . Can you please advise ? -- Karthik
RK
Roland Klabunde
Mon, Aug 25, 2008 7:29 PM

This is most likely due to limitations of your mobile provider. Most
providers do not allow you to use GPRS/EDGE/HSDPA connections together
with SIP, RTP (because this offends their business models).

Regards

Karthik Babu schrieb:

Hello Nanang ,

I have just noticed that the registration is failing and could not use
the app  using GPRS (tested on both  e61 and n95 ) .

Can you please advise ?

--
Karthik


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

This is most likely due to limitations of your mobile provider. Most providers do not allow you to use GPRS/EDGE/HSDPA connections together with SIP, RTP (because this offends their business models). Regards Karthik Babu schrieb: > Hello Nanang , > > I have just noticed that the registration is failing and could not use > the app using GPRS (tested on both e61 and n95 ) . > > > Can you please advise ? > > > > > > > -- > Karthik > ------------------------------------------------------------------------ > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
FP
Fabio Pietrosanti (naif)
Mon, Aug 25, 2008 7:59 PM

Which kind of methods for the detection are known to be in place?

I mean, they simply block 5060 udp/tcp port or do they use some kind of
protocol detection systems to catch RTP and SIP protocol even of other
udp/tcp ports?

Because that's a very interesting item for all the mobile voip
capabilities, and if protocol detection is employed then some kind of
open obfuscation technology could be evaluated for voip traffic.

Let me know

Fabio

Roland Klabunde wrote:

This is most likely due to limitations of your mobile provider. Most
providers do not allow you to use GPRS/EDGE/HSDPA connections together
with SIP, RTP (because this offends their business models).

Regards

Karthik Babu schrieb:

Hello Nanang ,

I have just noticed that the registration is failing and could not use
the app  using GPRS (tested on both  e61 and n95 ) .

Can you please advise ?

--
Karthik


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

Which kind of methods for the detection are known to be in place? I mean, they simply block 5060 udp/tcp port or do they use some kind of protocol detection systems to catch RTP and SIP protocol even of other udp/tcp ports? Because that's a very interesting item for all the mobile voip capabilities, and if protocol detection is employed then some kind of open obfuscation technology could be evaluated for voip traffic. Let me know Fabio Roland Klabunde wrote: > This is most likely due to limitations of your mobile provider. Most > providers do not allow you to use GPRS/EDGE/HSDPA connections together > with SIP, RTP (because this offends their business models). > > Regards > > > Karthik Babu schrieb: > >> Hello Nanang , >> >> I have just noticed that the registration is failing and could not use >> the app using GPRS (tested on both e61 and n95 ) . >> >> >> Can you please advise ? >> >> >> >> >> >> >> -- >> Karthik >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip@lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> >> > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
RK
Roland Klabunde
Mon, Aug 25, 2008 10:37 PM

Reviewing your questions, I'm not that confident anymore, that my
initial statement was right. While answering to the initial post, I
recalled some posts from the german IPPhone-Forum, I read one or two
years ago. Seemed, that most of the technical limitations being in place
that time are no longer existent. I tried to doublecheck this, but I
couldn't find any clue about any significant technical brake for SIP.
Just T&C's against SIP and some technical limitations (bandwidth, prices
etc.)

I would like to withdraw my statement and park it for further
investigations :)

Regards

Which kind of methods for the detection are known to be in place?

I mean, they simply block 5060 udp/tcp port or do they use some kind of
protocol detection systems to catch RTP and SIP protocol even of other
udp/tcp ports?

Because that's a very interesting item for all the mobile voip
capabilities, and if protocol detection is employed then some kind of
open obfuscation technology could be evaluated for voip traffic.

Let me know

Fabio

Roland Klabunde wrote:

This is most likely due to limitations of your mobile provider. Most
providers do not allow you to use GPRS/EDGE/HSDPA connections together
with SIP, RTP (because this offends their business models).

Regards

Karthik Babu schrieb:

Hello Nanang ,

I have just noticed that the registration is failing and could not use
the app  using GPRS (tested on both  e61 and n95 ) .

Can you please advise ?

--
Karthik


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

Reviewing your questions, I'm not that confident anymore, that my initial statement was right. While answering to the initial post, I recalled some posts from the german IPPhone-Forum, I read one or two years ago. Seemed, that most of the technical limitations being in place that time are no longer existent. I tried to doublecheck this, but I couldn't find any clue about any significant technical brake for SIP. Just T&C's against SIP and some technical limitations (bandwidth, prices etc.) I would like to withdraw my statement and park it for further investigations :) Regards > Which kind of methods for the detection are known to be in place? > > I mean, they simply block 5060 udp/tcp port or do they use some kind of > protocol detection systems to catch RTP and SIP protocol even of other > udp/tcp ports? > > Because that's a very interesting item for all the mobile voip > capabilities, and if protocol detection is employed then some kind of > open obfuscation technology could be evaluated for voip traffic. > > Let me know > > Fabio > > Roland Klabunde wrote: > >> This is most likely due to limitations of your mobile provider. Most >> providers do not allow you to use GPRS/EDGE/HSDPA connections together >> with SIP, RTP (because this offends their business models). >> >> Regards >> >> >> Karthik Babu schrieb: >> >> >>> Hello Nanang , >>> >>> I have just noticed that the registration is failing and could not use >>> the app using GPRS (tested on both e61 and n95 ) . >>> >>> >>> Can you please advise ? >>> >>> >>> >>> >>> >>> >>> -- >>> Karthik >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Visit our blog: http://blog.pjsip.org >>> >>> pjsip mailing list >>> pjsip@lists.pjsip.org >>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >>> >>> >>> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip@lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> >> > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
JK
Jeremy King
Sun, Aug 31, 2008 3:36 AM

You could use a packet sniffer on your device to figure out what is
happening.

  • J

On Tue, Aug 26, 2008 at 4:07 AM, Roland Klabunde <roland.klabunde@freenet.de

wrote:

Reviewing your questions, I'm not that confident anymore, that my
initial statement was right. While answering to the initial post, I
recalled some posts from the german IPPhone-Forum, I read one or two
years ago. Seemed, that most of the technical limitations being in place
that time are no longer existent. I tried to doublecheck this, but I
couldn't find any clue about any significant technical brake for SIP.
Just T&C's against SIP and some technical limitations (bandwidth, prices
etc.)

I would like to withdraw my statement and park it for further
investigations :)

Regards

Which kind of methods for the detection are known to be in place?

I mean, they simply block 5060 udp/tcp port or do they use some kind of
protocol detection systems to catch RTP and SIP protocol even of other
udp/tcp ports?

Because that's a very interesting item for all the mobile voip
capabilities, and if protocol detection is employed then some kind of
open obfuscation technology could be evaluated for voip traffic.

Let me know

Fabio

Roland Klabunde wrote:

This is most likely due to limitations of your mobile provider. Most
providers do not allow you to use GPRS/EDGE/HSDPA connections together
with SIP, RTP (because this offends their business models).

Regards

Karthik Babu schrieb:

Hello Nanang ,

I have just noticed that the registration is failing and could not use
the app  using GPRS (tested on both  e61 and n95 ) .

Can you please advise ?

--
Karthik


You could use a packet sniffer on your device to figure out what is happening. - J On Tue, Aug 26, 2008 at 4:07 AM, Roland Klabunde <roland.klabunde@freenet.de > wrote: > Reviewing your questions, I'm not that confident anymore, that my > initial statement was right. While answering to the initial post, I > recalled some posts from the german IPPhone-Forum, I read one or two > years ago. Seemed, that most of the technical limitations being in place > that time are no longer existent. I tried to doublecheck this, but I > couldn't find any clue about any significant technical brake for SIP. > Just T&C's against SIP and some technical limitations (bandwidth, prices > etc.) > > I would like to withdraw my statement and park it for further > investigations :) > > Regards > > > > > Which kind of methods for the detection are known to be in place? > > > > I mean, they simply block 5060 udp/tcp port or do they use some kind of > > protocol detection systems to catch RTP and SIP protocol even of other > > udp/tcp ports? > > > > Because that's a very interesting item for all the mobile voip > > capabilities, and if protocol detection is employed then some kind of > > open obfuscation technology could be evaluated for voip traffic. > > > > Let me know > > > > Fabio > > > > Roland Klabunde wrote: > > > >> This is most likely due to limitations of your mobile provider. Most > >> providers do not allow you to use GPRS/EDGE/HSDPA connections together > >> with SIP, RTP (because this offends their business models). > >> > >> Regards > >> > >> > >> Karthik Babu schrieb: > >> > >> > >>> Hello Nanang , > >>> > >>> I have just noticed that the registration is failing and could not use > >>> the app using GPRS (tested on both e61 and n95 ) . > >>> > >>> > >>> Can you please advise ? > >>> > >>> > >>> > >>> > >>> > >>> > >>> -- > >>> Karthik > >>> > ------------------------------------------------------------------------ > >>> > >>> _______________________________________________ > >>> Visit our blog: http://blog.pjsip.org > >>> > >>> pjsip mailing list > >>> pjsip@lists.pjsip.org > >>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >>> > >>> > >>> > >> _______________________________________________ > >> Visit our blog: http://blog.pjsip.org > >> > >> pjsip mailing list > >> pjsip@lists.pjsip.org > >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >> > >> > > > > > > _______________________________________________ > > Visit our blog: http://blog.pjsip.org > > > > pjsip mailing list > > pjsip@lists.pjsip.org > > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
AR
Archie Rosenblum
Sun, Aug 31, 2008 10:49 PM

How do I detect if codec negotiation fails?  For example, I want to try G729
first, so I disable all other codecs, and attempt a connection.  If this
fails, I would like to enable other codecs and try again.  (I did alter the
codec priority, but the upstream server seems pick a higher bandwidth
codec.)

Best regards,

Archie

How do I detect if codec negotiation fails? For example, I want to try G729 first, so I disable all other codecs, and attempt a connection. If this fails, I would like to enable other codecs and try again. (I did alter the codec priority, but the upstream server seems pick a higher bandwidth codec.) Best regards, Archie
NI
Nanang Izzuddin
Wed, Sep 3, 2008 4:27 PM

Hi,

I think it could only be done by examining the response from UAS,
while it may vary among the SIP implementations, for ex: PJSUA will
respond with 488 and a specific warning. The best way should be
setting the UAS to regard the UAC codecs priority, if that's possible.

Regards,
nanang

On 01/09/2008, Archie Rosenblum archie@bbsti.com wrote:

How do I detect if codec negotiation fails?  For example, I want to try G729
first, so I disable all other codecs, and attempt a connection.  If this
fails, I would like to enable other codecs and try again.  (I did alter the
codec priority, but the upstream server seems pick a higher bandwidth
codec.)

Best regards,

Archie


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

Hi, I think it could only be done by examining the response from UAS, while it may vary among the SIP implementations, for ex: PJSUA will respond with 488 and a specific warning. The best way should be setting the UAS to regard the UAC codecs priority, if that's possible. Regards, nanang On 01/09/2008, Archie Rosenblum <archie@bbsti.com> wrote: > > > > > > How do I detect if codec negotiation fails? For example, I want to try G729 > first, so I disable all other codecs, and attempt a connection. If this > fails, I would like to enable other codecs and try again. (I did alter the > codec priority, but the upstream server seems pick a higher bandwidth > codec.) > > > > Best regards, > > Archie > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >
AR
Archie Rosenblum
Wed, Sep 3, 2008 8:58 PM

Thank you.

-----Original Message-----
From: pjsip-bounces@lists.pjsip.org [mailto:pjsip-bounces@lists.pjsip.org]
On Behalf Of Nanang Izzuddin
Sent: Wednesday, September 03, 2008 12:27 PM
To: pjsip list
Subject: Re: [pjsip] Codec Negotiation Failure Detection

Hi,

I think it could only be done by examining the response from UAS,
while it may vary among the SIP implementations, for ex: PJSUA will
respond with 488 and a specific warning. The best way should be
setting the UAS to regard the UAC codecs priority, if that's possible.

Regards,
nanang

On 01/09/2008, Archie Rosenblum archie@bbsti.com wrote:

How do I detect if codec negotiation fails?  For example, I want to try

G729

first, so I disable all other codecs, and attempt a connection.  If this
fails, I would like to enable other codecs and try again.  (I did alter

the

codec priority, but the upstream server seems pick a higher bandwidth
codec.)

Best regards,

Archie


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org



This email has been scanned by the MxScan Email Security System.


Thank you. -----Original Message----- From: pjsip-bounces@lists.pjsip.org [mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Nanang Izzuddin Sent: Wednesday, September 03, 2008 12:27 PM To: pjsip list Subject: Re: [pjsip] Codec Negotiation Failure Detection Hi, I think it could only be done by examining the response from UAS, while it may vary among the SIP implementations, for ex: PJSUA will respond with 488 and a specific warning. The best way should be setting the UAS to regard the UAC codecs priority, if that's possible. Regards, nanang On 01/09/2008, Archie Rosenblum <archie@bbsti.com> wrote: > > > > > > How do I detect if codec negotiation fails? For example, I want to try G729 > first, so I disable all other codecs, and attempt a connection. If this > fails, I would like to enable other codecs and try again. (I did alter the > codec priority, but the upstream server seems pick a higher bandwidth > codec.) > > > > Best regards, > > Archie > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > _______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip@lists.pjsip.org http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org ---------------------------------------------------------------------------- --------- This email has been scanned by the MxScan Email Security System. ---------------------------------------------------------------------------- ---------
AR
Archie Rosenblum
Fri, Sep 5, 2008 2:42 PM

Does anyone have a method to detect a busy signal (regular and fast busy)?

Best regards,
Archie

Does anyone have a method to detect a busy signal (regular and fast busy)? Best regards, Archie