[sr-dev] SIP-I ?

Torrey Searle tsearle at gmail.com
Thu Mar 28 14:30:03 CET 2013


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 at evaristesys.com> wrote:
> Yes, but don't elements of the MIME body get copied into the SIP responses by the UAS?
>
>
> Javi Gallart <jgallart at 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 at 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 at lists.sip-router.org
>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>>
>>
>>_______________________________________________
>>sr-dev mailing list
>>sr-dev at 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 at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev



More information about the sr-dev mailing list