Hi list
this may sound like and old ugly topic, but at the end of the day most of the traffic still starts/terminates in TDM networks. For those not familiar with it, the IPX (http://en.wikipedia.org/wiki/IP_exchange) mandates the usage of SIP-I between operators for transporting the call information over SIP. Kamailio is the core component of our infrastructure, and in order to route traffic between these kind of operators we might need to "understand" somehow SIP-I. So this is more or less like an open question: do you think it makes sense to write a kamailio module for decoding/encoding ISUP/MAP traffic, or do you think it fits better in another type of equipment closer to the "TDM border" (Yate, Freeswitch,...).
Thanks in advance
Javi
Hi Javi,
The first question to ask is: if Kamailio could understand ISUP parameters, what would it do with them?
If the answer is "not a whole lot", chances are it is something that only needs to be understood by the endpoints, and which Kamailio would continue to be agnostic to, as it is now. Kamailio is, above all else, a message relay.
-- Alex
Thanks Alex
the first thing that came to my mind is performing some number manipulation. Imagine kamailio acting as a router for several carriers. One of them demands an international NOA with a weird prefix, whereas the other one, for the same destination, requires a pound (#) at the end, and so on. I agree with you in disliking idea of being too "invasive" in the body of the sip message, but it's something already doable for instance with SDP.
Javi On 03/22/2013 02:50 PM, Alex Balashov wrote:
Hi Javi,
The first question to ask is: if Kamailio could understand ISUP parameters, what would it do with them?
If the answer is "not a whole lot", chances are it is something that only needs to be understood by the endpoints, and which Kamailio would continue to be agnostic to, as it is now. Kamailio is, above all else, a message relay.
-- Alex
Yes, but what happens when those modifications, or responses based on those modifications, are returned to the sender? Much as with most SIP headers, the sending SS7 gateway can well say, "I didn't send that."
Javi Gallart jgallart@systemonenoc.com wrote:
Thanks Alex
the first thing that came to my mind is performing some number manipulation. Imagine kamailio acting as a router for several carriers.
One of them demands an international NOA with a weird prefix, whereas the other one, for the same destination, requires a pound (#) at the end, and so on. I agree with you in disliking idea of being too "invasive" in the body of the sip message, but it's something already doable for instance with SDP.
Javi On 03/22/2013 02:50 PM, Alex Balashov wrote:
Hi Javi,
The first question to ask is: if Kamailio could understand ISUP parameters, what would it do with them?
If the answer is "not a whole lot", chances are it is something that only needs to be understood by the endpoints, and which Kamailio
would
continue to be agnostic to, as it is now. Kamailio is, above all else, a message relay.
-- Alex
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Someone else approached me at Fosdem (iirc), saying they are working on (or already have) a module to deal with SIP-I, but it may not actually happen to get it from there (unless the person is here and can confirm more).
Anyhow, adding in a new module is ok as long as there is a maintainer for it in the first year. Most of my modules were added because I needed them, not because there was another potential user. In this case, as said above, I expect more to use it, but that does not matter at the end. So I would find it useful to have.
Just for sake of completeness, besides the maintainer rule, the only constraint for modules would be not to be something very specific just for a private use case (e.g., a connector to an internal system, not available to others at all, with custom protocol and no chance for additional use cases). Not the case here, of course, being actually about a recognized standard.
Cheers, Daniel
On 3/22/13 3:27 PM, Alex Balashov wrote:
Yes, but what happens when those modifications, or responses based on those modifications, are returned to the sender? Much as with most SIP headers, the sending SS7 gateway can well say, "I didn't send that."
Javi Gallart jgallart@systemonenoc.com wrote:
Thanks Alex
the first thing that came to my mind is performing some number manipulation. Imagine kamailio acting as a router for several carriers.
One of them demands an international NOA with a weird prefix, whereas the other one, for the same destination, requires a pound (#) at the end, and so on. I agree with you in disliking idea of being too "invasive" in the body of the sip message, but it's something already doable for instance with SDP.
Javi On 03/22/2013 02:50 PM, Alex Balashov wrote:
Hi Javi,
The first question to ask is: if Kamailio could understand ISUP parameters, what would it do with them?
If the answer is "not a whole lot", chances are it is something that only needs to be understood by the endpoints, and which Kamailio
would
continue to be agnostic to, as it is now. Kamailio is, above all else, a message relay.
-- Alex
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hi Daniel
understood. We haven't developed anything yet, I wanted to know the general opinion about the convenience of writing a module of such nature in kamailiio. By the way, it that person is "listening", it would be nice if we can get in touch.
Regards
Javi On 03/22/2013 03:53 PM, Daniel-Constantin Mierla wrote:
Someone else approached me at Fosdem (iirc), saying they are working on (or already have) a module to deal with SIP-I, but it may not actually happen to get it from there (unless the person is here and can confirm more).
Anyhow, adding in a new module is ok as long as there is a maintainer for it in the first year. Most of my modules were added because I needed them, not because there was another potential user. In this case, as said above, I expect more to use it, but that does not matter at the end. So I would find it useful to have.
Just for sake of completeness, besides the maintainer rule, the only constraint for modules would be not to be something very specific just for a private use case (e.g., a connector to an internal system, not available to others at all, with custom protocol and no chance for additional use cases). Not the case here, of course, being actually about a recognized standard.
Cheers, Daniel
On 3/22/13 3:27 PM, Alex Balashov wrote:
Yes, but what happens when those modifications, or responses based on those modifications, are returned to the sender? Much as with most SIP headers, the sending SS7 gateway can well say, "I didn't send that."
Javi Gallart jgallart@systemonenoc.com wrote:
Thanks Alex
the first thing that came to my mind is performing some number manipulation. Imagine kamailio acting as a router for several carriers.
One of them demands an international NOA with a weird prefix, whereas the other one, for the same destination, requires a pound (#) at the end, and so on. I agree with you in disliking idea of being too "invasive" in the body of the sip message, but it's something already doable for instance with SDP.
Javi On 03/22/2013 02:50 PM, Alex Balashov wrote:
Hi Javi,
The first question to ask is: if Kamailio could understand ISUP parameters, what would it do with them?
If the answer is "not a whole lot", chances are it is something that only needs to be understood by the endpoints, and which Kamailio
would
continue to be agnostic to, as it is now. Kamailio is, above all else, a message relay.
-- Alex
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hi
this is really a common practice among carriers. Actually the SS7 case is easier because, unlike in SIP with the To, From..., in a regular ISUP call the details of the initiating call are not sent in the backwards direction: an ANM message indicating the call was answered doesn't carry the numbers in the IAM that initiates the call. So it's a matter of billing properly and accurately.
Javi On 03/22/2013 03:27 PM, Alex Balashov wrote:
Yes, but what happens when those modifications, or responses based on those modifications, are returned to the sender? Much as with most SIP headers, the sending SS7 gateway can well say, "I didn't send that."
Javi Gallart jgallart@systemonenoc.com wrote:
Thanks Alex
the first thing that came to my mind is performing some number manipulation. Imagine kamailio acting as a router for several carriers.
One of them demands an international NOA with a weird prefix, whereas the other one, for the same destination, requires a pound (#) at the end, and so on. I agree with you in disliking idea of being too "invasive" in the body of the sip message, but it's something already doable for instance with SDP.
Javi On 03/22/2013 02:50 PM, Alex Balashov wrote:
Hi Javi,
The first question to ask is: if Kamailio could understand ISUP parameters, what would it do with them?
If the answer is "not a whole lot", chances are it is something that only needs to be understood by the endpoints, and which Kamailio
would
continue to be agnostic to, as it is now. Kamailio is, above all else, a message relay.
-- Alex
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Yes, but don't elements of the MIME body get copied into the SIP responses by the UAS?
Javi Gallart jgallart@systemonenoc.com wrote:
Hi
this is really a common practice among carriers. Actually the SS7 case is easier because, unlike in SIP with the To, From..., in a regular ISUP call the details of the initiating call are not sent in the backwards direction: an ANM message indicating the call was answered doesn't carry the numbers in the IAM that initiates the call. So it's a matter of billing properly and accurately.
Javi On 03/22/2013 03:27 PM, Alex Balashov wrote:
Yes, but what happens when those modifications, or responses based on
those modifications, are returned to the sender? Much as with most SIP headers, the sending SS7 gateway can well say, "I didn't send that."
Javi Gallart jgallart@systemonenoc.com wrote:
Thanks Alex
the first thing that came to my mind is performing some number manipulation. Imagine kamailio acting as a router for several
carriers.
One of them demands an international NOA with a weird prefix,
whereas
the other one, for the same destination, requires a pound (#) at the end, and so on. I agree with you in disliking idea of being too "invasive" in the body of the sip message, but it's something
already
doable for instance with SDP.
Javi On 03/22/2013 02:50 PM, Alex Balashov wrote:
Hi Javi,
The first question to ask is: if Kamailio could understand ISUP parameters, what would it do with them?
If the answer is "not a whole lot", chances are it is something
that
only needs to be understood by the endpoints, and which Kamailio
would
continue to be agnostic to, as it is now. Kamailio is, above all else, a message relay.
-- Alex
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hi,
I have some code for updating the destination number and the NAI of an ISUP message encoded in a SIP message and would be interested in submitting it as a module to Kamailio. Could I get more information on guidelines and procedure for submitting a module?
Regards, Torrey
On 22 March 2013 16:49, Alex Balashov abalashov@evaristesys.com wrote:
Yes, but don't elements of the MIME body get copied into the SIP responses by the UAS?
Javi Gallart jgallart@systemonenoc.com wrote:
Hi
this is really a common practice among carriers. Actually the SS7 case is easier because, unlike in SIP with the To, From..., in a regular ISUP call the details of the initiating call are not sent in the backwards direction: an ANM message indicating the call was answered doesn't carry the numbers in the IAM that initiates the call. So it's a matter of billing properly and accurately.
Javi On 03/22/2013 03:27 PM, Alex Balashov wrote:
Yes, but what happens when those modifications, or responses based on
those modifications, are returned to the sender? Much as with most SIP headers, the sending SS7 gateway can well say, "I didn't send that."
Javi Gallart jgallart@systemonenoc.com wrote:
Thanks Alex
the first thing that came to my mind is performing some number manipulation. Imagine kamailio acting as a router for several
carriers.
One of them demands an international NOA with a weird prefix,
whereas
the other one, for the same destination, requires a pound (#) at the end, and so on. I agree with you in disliking idea of being too "invasive" in the body of the sip message, but it's something
already
doable for instance with SDP.
Javi On 03/22/2013 02:50 PM, Alex Balashov wrote:
Hi Javi,
The first question to ask is: if Kamailio could understand ISUP parameters, what would it do with them?
If the answer is "not a whole lot", chances are it is something
that
only needs to be understood by the endpoints, and which Kamailio
would
continue to be agnostic to, as it is now. Kamailio is, above all else, a message relay.
-- Alex
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Sent from my mobile, and thus lacking in the refinement one might expect from a fully-fledged keyboard.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-
Alex Balashov -
Daniel-Constantin Mierla -
Javi Gallart -
Torrey Searle