[Spce-user] Spce-user Digest, Vol 28, Issue 25

Developing Tomorrow nh.developer at gmail.com
Thu Mar 14 11:35:25 EDT 2013


Well, issue is "resolved"

Apparently on a fresh install, if you do not define the prefix properly, 
Sipwise will not let you call an unformatted number.
I have tried to dial my mobile number directly , but it did not work.
But putting 00 is would recognize the format and go thru...

So lesson is that all small details count.

Thank you for the assistance



_________________________________________________________________________
Please consider the environment before printing this email.
 
Notice: Please do not include customer identifying information (i.e.,
account number, social security, etc.) in email communications.
 
Privacy Statement: This message may contain confidential information that is
protected by law. If you received this message in error, please notify the
sender by fax or email and delete this message. If you properly received
this message, you may use its contents only in strictaccordance with our
instructions and privacy policy.
If any person makes a false or misleading representation to obtain customer
information, that person may have committed a federal crime, and we may
report that person to the proper authorities.

-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of
spce-user-request at lists.sipwise.com
Sent: 14 March 2013 15:39
To: spce-user at lists.sipwise.com
Subject: Spce-user Digest, Vol 28, Issue 25

Send Spce-user mailing list submissions to
	spce-user at lists.sipwise.com

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.sipwise.com/listinfo/spce-user
or, via email, send a message with subject or body 'help' to
	spce-user-request at lists.sipwise.com

You can reach the person managing the list at
	spce-user-owner at lists.sipwise.com

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Spce-user digest..."


Today's Topics:

   1. media packets not travelling properly (Developing Tomorrow)
   2. media packets not travelling properly (Developing Tomorrow)
   3. Re: media packets not travelling properly (Daniel Grotti)
   4. Problem (Bug?) in Billing Fee uploads (Gavin Sweet)
   5. Re: Problem (Bug?) in Billing Fee uploads (Gavin Sweet)


----------------------------------------------------------------------

Message: 1
Date: Thu, 14 Mar 2013 12:34:17 +0100
From: "Developing Tomorrow" <nh.developer at gmail.com>
Subject: [Spce-user] media packets not travelling properly
To: <spce-user at lists.sipwise.com>
Message-ID: <00ba01ce20a7$dd924120$98b6c360$@gmail.com>
Content-Type: text/plain; charset="us-ascii"

Hi.,

 

This is my first mail to this mailing list, so please forgive my erroneous
procedure if it might be.

 

I have installed sipwise CE, with some pains but it does the job.

If I use a provider connected over normal line (any normal sip provider)

The signalling is done properly I can see the messages, but then the audio
is not following.

 

By that I mean I cannot hear the ringtone nor can I hear the other party
talking, nor they can hear me.

 

I have tried over a vpn, and I have one way audio.

 

The system is installed on a public server with the default iptables.

I have created only 1 domain that receive the external connections on port
5060

 

On the other hand, I have a vpn conection to a foreign network.

Client-----XXXXX (public ip) ----------provider********************* no
audio nor A nor B leg.

Client-----XXXXX(public ip)----------VPN_start
(10.8.0.1)-------------VPN_end(10.8.0.6)-----------provider (172.26.10.2
[not real])******** 1 way audio, they do not hear me

 

Anybody can shade a light here?

 

Thx

herve

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.sipwise.com/pipermail/spce-user/attachments/20130314/ce2315ab/
attachment-0001.htm>

------------------------------

Message: 2
Date: Thu, 14 Mar 2013 12:26:41 +0100
From: "Developing Tomorrow" <nh.developer at gmail.com>
Subject: [Spce-user] media packets not travelling properly
To: <spce-user at lists.sipwise.com>
Message-ID: <00b501ce20a6$cdbdefc0$6939cf40$@gmail.com>
Content-Type: text/plain; charset="us-ascii"

Hi.,

 

This is my first mail to this mailing list, so please forgive my erroneous
procedure if it might be.

 

I have installed sipwise CE, with some pains but it does the job.

If I use a provider connected over normal line (any normal sip provider)

The signalling is done properly I can see the messages, but then the audio
is not following.

 

By that I mean I cannot hear the ringtone nor can I hear the other party
talking, nor they can hear me.

 

I have tried over a vpn, and I have one way audio.

 

The system is installed on a public server with the default iptables.

I have created only 1 domain that receive the external connections on port
5060

 

On the other hand, I have a vpn conection to a foreign network.

Client-----XXXXX (public ip) ----------provider********************* no
audio nor A nor B leg.

Client-----XXXXX(public ip)----------VPN_start
(10.8.0.1)-------------VPN_end(10.8.0.6)-----------provider (172.26.10.2
[not real])******** 1 way audio, they do not hear me

 

Anybody can shade a light here?

 

Thx

herve

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.sipwise.com/pipermail/spce-user/attachments/20130314/07c29be2/
attachment-0001.htm>

------------------------------

Message: 3
Date: Thu, 14 Mar 2013 12:49:01 +0100
From: Daniel Grotti <dgrotti at sipwise.com>
Subject: Re: [Spce-user] media packets not travelling properly
To: spce-user at lists.sipwise.com
Message-ID: <5141B92D.7010105 at sipwise.com>
Content-Type: text/plain; charset="iso-8859-1"

On 03/14/2013 12:34 PM, Developing Tomorrow wrote:
>
> Hi.,
>
>  
>
> This is my first mail to this mailing list, so please forgive my 
> erroneous procedure if it might be.
>
>  
>
> I have installed sipwise CE, with some pains but it does the job.
>
> If I use a provider connected over normal line (any normal sip 
> provider)
>
> The signalling is done properly I can see the messages, but then the 
> audio is not following.
>
>  
>
> By that I mean I cannot hear the ringtone nor can I hear the other 
> party talking, nor they can hear me.
>
>  
>
> I have tried over a vpn, and I have one way audio.
>
>  
>
> The system is installed on a public server with the default iptables.
>
> I have created only 1 domain that receive the external connections on 
> port 5060
>
>  
>
> On the other hand, I have a vpn conection to a foreign network.
>
> Client-----XXXXX (public ip) ----------provider*********************
> no audio nor A nor B leg.
>
> Client-----XXXXX(public ip)----------VPN_start 
> (10.8.0.1)-------------VPN_end(10.8.0.6)-----------provider
> (172.26.10.2 [not real])******** 1 way audio, they do not hear me
>
>  
>
> Anybody can shade a light here?
>
>  
>
> Thx
>
> herve
>
>  
>
>  
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user


Hi Herve,
please check your mediaproxy process, is it running properly (ps -ef | grep
mediaproxy) and listening on your public IP ?
If the client is behind nat, please make sure it's not using any kind on
STUN server to discover its own public IP, or ICE or whatever, NAT stuffs
are handled by NGCP.

Try to run ngrep-sip and check the SIP messages. SDP part of INVITE to
provider and of 200 OK to the client should contain the mediaproxy's public
IP.


Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.sipwise.com/pipermail/spce-user/attachments/20130314/be920fb1/
attachment-0001.htm>

------------------------------

Message: 4
Date: Thu, 14 Mar 2013 12:51:15 -0000
From: "Gavin Sweet" <gavin.sweet at skyracktelecom.com>
Subject: [Spce-user] Problem (Bug?) in Billing Fee uploads
To: <spce-user at lists.sipwise.com>
Message-ID: <05c801ce20b2$9d760cb0$d8622610$@sweet at skyracktelecom.com>
Content-Type: text/plain;	charset="us-ascii"

Hi -
I have had some problems with destination regex support when uploading
Billing Fees using the batch Upload file function in the Admin GUI.
I have tested these problems with very small file uploads to ensure its not
a problem with file size/transfer etc.
I actually started off trying to ensure an exact match for the number
44118555, which should be simply ^44118555$ - however this doesn't upload.
I then investigated further and found some unexpected results as below. If
anyone can help, or let me know that this is a bug, that would be great.
Manual definition of these fees is not an option for workaround as we have
over 30000 records. An odd (inelegant) form of regex may force it to work,
but that's not what I'd prefer.

Other than case 7 and 8 which I tried for completeness, I think all the
below should work, but they don't.
----------------------------------------------------------------------------
---------------------
Case       Uploaded fee (csv record)                                  =>
Destination (in profile)
----------------------------------------------------------------------------
---------------------
1 (ok)     ^*.$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0                         =>
^*.$
2 (ok)     ^44118555.$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0                  =>
^44118555.$
3 (ok)     ^44118[1-9][0-9][0-9]$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0       =>
^44118[1-9][0-9][0-9]$
4 (ok)     ^4411855[5]$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0                 =>
^4411855[5]$
5 (fail)   ^44118555.*$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0                 =>
44118555
6 (fail)   ^44118555$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0                   =>
44118555
7 (fail)   '^44118555$',ABC,ABC,0,1,0.5,1,0,1,0.5,1,0                 =>
'^44118555$'
8 (fail)   "^44118555$",ABC,ABC,0,1,0.5,1,0,1,0.5,1,0                 =>
"^44118555$"
----------------------------------------------------------------------------
---------------------

Thanks,
Gavin




------------------------------

Message: 5
Date: Thu, 14 Mar 2013 14:38:40 -0000
From: "Gavin Sweet" <gavin.sweet at skyracktelecom.com>
Subject: Re: [Spce-user] Problem (Bug?) in Billing Fee uploads
To: <spce-user at lists.sipwise.com>
Message-ID: <063801ce20c1$9f1da460$dd58ed20$@sweet at skyracktelecom.com>
Content-Type: text/plain;	charset="us-ascii"

My table of tests got a bit mangled.
Basically, this problem is when trying to upload fees from file. 
For example, for *exactly* 44118555, the destination should be: ^44118555$
But the ^ and $ get stripped for some reason during the upload from file.
Same with ^44118555.*$
But NOT with ^4411855[5]$ or  ^44118555.$

Cheers
Gavin

> -----Original Message-----
> From: spce-user-bounces at lists.sipwise.com [mailto:spce-user- 
> bounces at lists.sipwise.com] On Behalf Of Gavin Sweet
> Sent: 14 March 2013 12:51
> To: spce-user at lists.sipwise.com
> Subject: [Spce-user] Problem (Bug?) in Billing Fee uploads
> 
> Hi -
> I have had some problems with destination regex support when uploading 
> Billing Fees using the batch Upload file function in the Admin GUI.
> I have tested these problems with very small file uploads to ensure 
> its not a problem with file size/transfer etc.
> I actually started off trying to ensure an exact match for the number 
> 44118555, which should be simply ^44118555$ - however this doesn't 
> upload.
> I then investigated further and found some unexpected results as below.
> If anyone can help, or let me know that this is a bug, that would be 
> great.
> Manual definition of these fees is not an option for workaround as we 
> have over 30000 records. An odd (inelegant) form of regex may force it 
> to work, but that's not what I'd prefer.
> 
> Other than case 7 and 8 which I tried for completeness, I think all 
> the below should work, but they don't.
> ----------------------------------------------------------------------
> -
> -----
> ---------------------
> Case       Uploaded fee (csv record)
> =>
> Destination (in profile)
> ----------------------------------------------------------------------
> -
> -----
> ---------------------
> 1 (ok)     ^*.$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0
> =>
> ^*.$
> 2 (ok)     ^44118555.$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0
> =>
> ^44118555.$
> 3 (ok)     ^44118[1-9][0-9][0-9]$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0
> =>
> ^44118[1-9][0-9][0-9]$
> 4 (ok)     ^4411855[5]$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0
> =>
> ^4411855[5]$
> 5 (fail)   ^44118555.*$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0
> =>
> 44118555
> 6 (fail)   ^44118555$,ABC,ABC,0,1,0.5,1,0,1,0.5,1,0
> =>
> 44118555
> 7 (fail)   '^44118555$',ABC,ABC,0,1,0.5,1,0,1,0.5,1,0
> =>
> '^44118555$'
> 8 (fail)   "^44118555$",ABC,ABC,0,1,0.5,1,0,1,0.5,1,0
> =>
> "^44118555$"
> ----------------------------------------------------------------------
> -
> -----
> ---------------------
> 
> Thanks,
> Gavin
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.2904 / Virus Database: 2641/6166 - Release Date:
> 03/12/13




------------------------------

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/listinfo/spce-user


End of Spce-user Digest, Vol 28, Issue 25
*****************************************





More information about the Spce-user mailing list