[OpenSIPS-Users] Example ENUM Query and Response Handling

Tue Sep 28 16:01:51 CEST 2010

Will enum_query automatically insert the response variables into the request-uri? Or do I have to pluck them out of the response and modify the request uri manually? 

On Sep 28, 2010, at 02:41 AM, users-request at lists.opensips.org wrote:

> Send Users mailing list submissions to
> users at lists.opensips.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> or, via email, send a message with subject or body 'help' to
> users-request at lists.opensips.org
>
> You can reach the person managing the list at
> users-owner at lists.opensips.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Users digest..."
>
>
> Today's Topics:
>
> 1. Re: SEAS connector for external AS (Bogdan-Andrei Iancu)
> 2. Re: SEAS connector for external AS (Thomas)
> 3. Re: SEAS connector for external AS (Bogdan-Andrei Iancu)
> 4. Re: SEAS connector for external AS (Bogdan-Andrei Iancu)
> 5. Re: Rewriting SIP Status in Reply (Ross McKillop)
> 6. Example ENUM Query and Response Handling (logan)
> 7. utf8 mysql DB charset (Kennard_White at logitech.com)
> 8. Re: openXCAP opensips-mi-proxy error (Franz Edler)
> 9. Re: Example ENUM Query and Response Handling (Bogdan-Andrei Iancu)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 27 Sep 2010 18:39:00 +0300
> From: Bogdan-Andrei Iancu <bogdan at voice-system.ro>
> Subject: Re: [OpenSIPS-Users] SEAS connector for external AS
> To: OpenSIPS users mailling list <users at lists.opensips.org>
> Message-ID: <4CA0BA94.4050203 at voice-system.ro>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Thomas,
>
> The idea of having a generic connector module (to be able to pass custom
> info from a SIP message to an external app) was really appealing to me
> several time. Something like SEAS - with the binary encoded format sent
> to other app - but no so linked to the logic in weSIP (the external app)....
>
> Anyhow, this will be automatically solved in opensips 2.0 where the
> routing script itself is an external application:
>
> http://www.opensips.org/Development/NewDesignDescription#toc2
>
> Regards,
> Bogdan
>
> Thomas wrote:
> >> I would be interested in whether what you are asking is possible to do
> >> with SIP/UDP. The proxy would have to be able to monitor (or being
> >> told about) the state of AS instances, and in case of failover, fix
> >> IPs in signaling (like in NAT traversal). This could actually be done
> >> on stateless lb proxy.
> >>
> >
> > Yes, IPs in signaling would be an issue then. I am not sure either that it is possible or even a good design option. The idea I had with a SEAS-like connector is to terminate the transport layer at OpenSIPS so that IP fixing is done the other way around i.e. by the application server (IP of OpenSIPS is used for Contact ... instead of internal IP). This would be similar to a SIP IPVS configuration I think. But as far as I understand now SEAS was not designed for this purpose and I would need to develop another OpenSIPS module, if it is possible to use OpenSIPS only for the transport layer.
> >
> >
>
>
> -- 
> Bogdan-Andrei Iancu
> OpenSIPS Bootcamp
> 15 - 19 November 2010, Edison, New Jersey, USA
> www.voice-system.ro
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 27 Sep 2010 18:18:17 +0200
> From: Thomas <thomas at cipango.org>
> Subject: Re: [OpenSIPS-Users] SEAS connector for external AS
> To: OpenSIPS users mailling list <users at lists.opensips.org>
> Message-ID: <B55EF763-6008-4430-8786-2BB86654638D at cipango.org>
> Content-Type: text/plain; charset=iso-8859-1
>
> Hi Bogdan,
>
> OpenSIPS 2.0 architecture sounds indeed appealing. The documentation reads that L0-L3 are mandatory, which means that Core module will always perform transaction management before dispatching incoming messages to the Routing Engine. Is my understanding correct ?
>
> Regards,
>
> Thomas
>
> Le 27 sept. 2010 ? 17:39, Bogdan-Andrei Iancu a ?crit :
>
> > Hi Thomas,
> >
> > The idea of having a generic connector module (to be able to pass custom
> > info from a SIP message to an external app) was really appealing to me
> > several time. Something like SEAS - with the binary encoded format sent
> > to other app - but no so linked to the logic in weSIP (the external app)....
> >
> > Anyhow, this will be automatically solved in opensips 2.0 where the
> > routing script itself is an external application:
> >
> > http://www.opensips.org/Development/NewDesignDescription#toc2
> >
> > Regards,
> > Bogdan
> >
> > Thomas wrote:
> >>> I would be interested in whether what you are asking is possible to do
> >>> with SIP/UDP. The proxy would have to be able to monitor (or being
> >>> told about) the state of AS instances, and in case of failover, fix
> >>> IPs in signaling (like in NAT traversal). This could actually be done
> >>> on stateless lb proxy.
> >>>
> >>
> >> Yes, IPs in signaling would be an issue then. I am not sure either that it is possible or even a good design option. The idea I had with a SEAS-like connector is to terminate the transport layer at OpenSIPS so that IP fixing is done the other way around i.e. by the application server (IP of OpenSIPS is used for Contact ... instead of internal IP). This would be similar to a SIP IPVS configuration I think But as far as I understand now SEAS was not designed for this purpose and I would need to develop another OpenSIPS module, if it is possible to use OpenSIPS only for the transport layer.
> >>
> >>
> >
> >
> > --
> > Bogdan-Andrei Iancu
> > OpenSIPS Bootcamp
> > 15 - 19 November 2010, Edison, New Jersey, USA
> > www.voice-system.ro
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 27 Sep 2010 19:46:27 +0300
> From: Bogdan-Andrei Iancu <bogdan at voice-system.ro>
> Subject: Re: [OpenSIPS-Users] SEAS connector for external AS
> To: OpenSIPS users mailling list <users at lists.opensips.org>
> Message-ID: <4CA0CA63.9060309 at voice-system.ro>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Elias,
>
> not sure if the port will make any sense in the future as with the new
> opensips 2.0 design, the seas module will become obsolete - WESIP as
> application will be able to connect directly to opensips core as a
> routing app. See:
> http://www.opensips.org/Development/NewDesignDescription#toc6
>
> No special connector will be required.
>
> Regards,
> Bogdan
>
> Elias Baixas wrote:
> > Hello Thomas,
> > at the moment I am refactoring the SEAS module to work with current sip-router, still haven't poked into current OpenSIPS to see how difficult the port will be, but expect to update it in the following months (after rework for sip-router is done).
> > well, SEAS is mainly composed of 2 parts:
> > *binary encoding of SIP messages so that application-server doesn't need to parse. The encoding contains a fast-lookup table for the main headers, and pointer-length-bytes for each part of each header, so you dont need to parse in the AS, you directly access the header at its pointer with it's lenght. (this also applies to URIs, parameters, headers, etc). There is code for encoding and decoding of this format in modules/seas directory.
> > *networking and transactional layer emulation: Since the transaction module is so much optimized, and will continue to be enhanced, we thought that a good option would be to let this layer (TL) in SER/OpenSER/OpenSIPs whatever and offer a TL API on the AS.
> >
> > yes this has its pros and cons as someone said, but it simplifies things for us, and also offers some performance gains at the AS (less SIP hops, less IPs).
> > You can use SEAS in transaction stateful or stateless as well, but we don't use stateless very much with WeSIP, so this hasn't been as much tested against real work.
> >
> > -It is intended to be generic, but since the only "backend" developed has been wesip, this is the main scenario that we have tested.
> > I would be very glad if more AS backends were developd (ruby, python, etc ), so you'd had my complete disposition to help ;)
> > anything else, don't hesitate to ask !
> > Elias
> > >Hello all,
> >
> > >I am the main developer of Cipango (http://www.cipango.org <http://www.cipango.org/>), an Open Source SIP-Servlets Application Server (with HTTP and Diameter support). We hav>e been using OpenSIPS together with Cipango in a couple of projects using plain vanilla SIP proxying from OpenSIPS to Cipango.
> > >We have found out the SEAS connector which allows for a direct connection between SIPS and an external SIP AS. Since we are also adding HA features >to Cipango, we were wondering whether this feature could be useful to have a front-end OpenSIPS distributing SIP messages to several SIP AS.
> >
> > >As a starting point, we had a look at the SEAS documentation (http://www.opensips.org/html/docs/modules/devel/seas.html). Since it has a few broken >links, we were wondering whether this module is still maintained and if it is intended to a be a generic one or mainly intended to weSIP ?
> >
> > >Regards,
> >
> > >Thomas
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
>
>
> -- 
> Bogdan-Andrei Iancu
> OpenSIPS Bootcamp
> 15 - 19 November 2010, Edison, New Jersey, USA
> www.voice-system.ro
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 27 Sep 2010 19:49:12 +0300
> From: Bogdan-Andrei Iancu <bogdan at voice-system.ro>
> Subject: Re: [OpenSIPS-Users] SEAS connector for external AS
> To: OpenSIPS users mailling list <users at lists.opensips.org>
> Message-ID: <4CA0CB08.40203 at voice-system.ro>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Thomas,
>
> the transaction layer will not be mandatory...it will be visited, but
> the routing logic may decide if transaction layer should be activated or
> not for that request.
>
> Regards,
> Bogdan
>
> Thomas wrote:
> > Hi Bogdan,
> >
> > OpenSIPS 2.0 architecture sounds indeed appealing. The documentation reads that L0-L3 are mandatory, which means that Core module will always perform transaction management before dispatching incoming messages to the Routing Engine. Is my understanding correct ?
> >
> > Regards,
> >
> > Thomas
> >
> > Le 27 sept. 2010 ? 17:39, Bogdan-Andrei Iancu a ?crit :
> >
> >
> >> Hi Thomas,
> >>
> >> The idea of having a generic connector module (to be able to pass custom
> >> info from a SIP message to an external app) was really appealing to me
> >> several time. Something like SEAS - with the binary encoded format sent
> >> to other app - but no so linked to the logic in weSIP (the external app)....
> >>
> >> Anyhow, this will be automatically solved in opensips 2.0 where the
> >> routing script itself is an external application:
> >>
> >> http://www.opensips.org/Development/NewDesignDescription#toc2
> >>
> >> Regards,
> >> Bogdan
> >>
> >> Thomas wrote:
> >>
> >>>> I would be interested in whether what you are asking is possible to do
> >>>> with SIP/UDP. The proxy would have to be able to monitor (or being
> >>>> told about) the state of AS instances, and in case of failover, fix
> >>>> IPs in signaling (like in NAT traversal). This could actually be done
> >>>> on stateless lb proxy.
> >>>>
> >>>>
> >>> Yes, IPs in signaling would be an issue then. I am not sure either that it is possible or even a good design option. The idea I had with a SEAS-like connector is to terminate the transport layer at OpenSIPS so that IP fixing is done the other way around i.e. by the application server (IP of OpenSIPS is used for Contact ... instead of internal IP). This would be similar to a SIP IPVS configuration I think. But as far as I understand now SEAS was not designed for this purpose and I would need to develop another OpenSIPS module, if it is possible to use OpenSIPS only for the transport layer.
> >>>
> >>>
> >>>
> >> --
> >> Bogdan-Andrei Iancu
> >> OpenSIPS Bootcamp
> >> 15 - 19 November 2010, Edison, New Jersey, USA
> >> www.voice-system.ro
> >>
> >>
> >> _______________________________________________
> >> Users mailing list
> >> Users at lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >>
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
>
>
> -- 
> Bogdan-Andrei Iancu
> OpenSIPS Bootcamp
> 15 - 19 November 2010, Edison, New Jersey, USA
> www.voice-system.ro
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 27 Sep 2010 18:09:13 +0100
> From: Ross McKillop <ross at ossiantelecom.co.uk>
> Subject: Re: [OpenSIPS-Users] Rewriting SIP Status in Reply
> To: OpenSIPS users mailling list <users at lists.opensips.org>
> Message-ID: <9F9B1380-ACFC-4E29-AD8D-8F645E8C59E4 at ossiantelecom.co.uk>
> Content-Type: text/plain; charset=us-ascii
>
>
> On 27 Sep 2010, at 15:53, Bogdan-Andrei Iancu wrote:
>
> > You can replace the negative replies only in failure route:
> >
> > Of course, the test can involve the check of a header from the received
> > reply.....
>
> Thanks for this - I had wrongly assumed that calling t_reply from the
> failure_route would result in the reply being sent to the box sending the
> failed status (if that makes sense) rather than the side which made the
> call in the first place.
>
> This should do what I'm looking for.
>
> Thanks again,
> Ross
>
>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 27 Sep 2010 18:17:49 +0000 (GMT)
> From: logan <voipmaster at me.com>
> Subject: [OpenSIPS-Users] Example ENUM Query and Response Handling
> To: users at lists.opensips.org
> Message-ID: <e2dfcc43-433e-ef06-e57d-8ff0a3d2cd44 at me.com>
> Content-Type: text/plain; charset="utf-8"
>
> Does anyone have an example of how to implement an ENUM Query, a sample of the response, and how to handle the response in the OpenSIPS cfg?
>
> Thank you in advance.?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.opensips.org/pipermail/users/attachments/20100927/3c53d940/attachment-0001.htm
>
> ------------------------------
>
> Message: 7
> Date: Mon, 27 Sep 2010 14:28:58 -0700
> From: Kennard_White at logitech.com
> Subject: [OpenSIPS-Users] utf8 mysql DB charset
> To: OpenSIPS users mailling list <users at lists.opensips.org>
> Message-ID:
> <OFA63051F5.AB180442-ON882577AB.00754F6A-882577AB.0076045F at logitech.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
>
> Hi,
>
> The script opensipsdbctl.mysql seems to go to some length to prevent UTF8
> charsets for the DB. Can anyone tell me why this is? E.g., what breaks with
> UTF8 tables?
>
> My current thinking is to make the charset a modparam of the db_mysql
> module, use mysql_options to set that charset, and then set the charset of
> the DB schema to be UTF8.
>
> Will this work?
>
> Thanks,
> Kennard
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.opensips.org/pipermail/users/attachments/20100927/cf40db41/attachment-0001.htm
>
> ------------------------------
>
> Message: 8
> Date: Tue, 28 Sep 2010 07:04:24 +0200
> From: "Franz Edler" <franz.edler at kabsi.at>
> Subject: Re: [OpenSIPS-Users] openXCAP opensips-mi-proxy error
> To: "'OpenSIPS users mailling list'" <users at lists.opensips.org>
> Message-ID: <000001cb5eca$9f36e210$dda4a630$@kabsi.at>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Anca,
>
> > Have you loaded presence_xcapdiff and pua modules? If yes, could you
> > please raise the debugging level in opensips to 6 and send the output?
>
> Thank's for your response.
> Meanwhile I found some errors in my configuration and now I am a step
> further but still have an issue with xcap_diff event.
>
> Maybe I will send another question on this when I need help.
>
> BR
> Franz
>
>
>
>
> ------------------------------
>
> Message: 9
> Date: Tue, 28 Sep 2010 09:41:47 +0300
> From: Bogdan-Andrei Iancu <bogdan at voice-system.ro>
> Subject: Re: [OpenSIPS-Users] Example ENUM Query and Response Handling
> To: OpenSIPS users mailling list <users at lists.opensips.org>
> Message-ID: <4CA18E2B.3040504 at voice-system.ro>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Logan,
>
> Just use the enum_query() from the ENUM module :
> http://www.opensipsorg/html/docs/modules/1.6.x/enum.html#id228376
>
> Regards,
> Bogdan
>
> logan wrote:
> > Does anyone have an example of how to implement an ENUM Query, a
> > sample of the response, and how to handle the response in the OpenSIPS
> > cfg?
> >
> > Thank you in advance.
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
>
>
> -- 
> Bogdan-Andrei Iancu
> OpenSIPS Bootcamp
> 15 - 19 November 2010, Edison, New Jersey, USA
> www.voice-system.ro
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> End of Users Digest, Vol 26, Issue 63
> *************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20100928/58c04d09/attachment-0001.htm 