[Serusers] INVITE retransmission

Zappasodi Daniele dzappasodi at seltatel.it
Tue Feb 15 12:17:36 CET 2005


Thanks Marian,
this is the function that I'm looking for.
Now my ser.cfg works correctly.

regards 
Daniele

-----Original Message-----
From: Marian Dumitru [mailto:marian.dumitru at voice-sistem.ro]
Sent: Tue 2/15/2005 10:42 AM
To: Zappasodi Daniele
Cc: Klaus Darilion; serusers at iptel.org
Subject: Re: [Serusers] INVITE retransmission
 
Hi Daniele,

if the transaction already exists (as created by t_newtran()), use 
t_forward_nonack_uri() instead of t_relay().

Best regards,
Marian

Zappasodi Daniele wrote:
> Hi Klaus,
> if I use t_newtran() and then I invoke the t_relay() to transmit the INVITE, I encounter this error message:
> t_newtran: transaction already in process
> and the proxy responds with 
> 500 : I'm terribly sorry, server error occurred.
> 
> Regards
> Daniele
> 
> -----Messaggio originale-----
> Da: Klaus Darilion [mailto:klaus.mailinglists at pernau.at]
> Inviato: martedì 15 febbraio 2005 9.33
> A: Zappasodi Daniele
> Cc: serusers at iptel.org
> Oggetto: Re: [Serusers] INVITE retransmission
> 
> 
> Hi!
> 
> If the first INVITE is processed by a function of the tm module, the 
> retransmissions will be absorbed by ser automatically.
> 
> take a look at:
> http://www.iptel.org/ser/doc/seruser/seruser.html#STATEFULUA
> 
> regards,
> klaus
> 
> Zappasodi Daniele wrote:
> 
> 
>>Hi,  
>>how can I distinguish, in ser.cfg, a retransmitted INVITE from the new INVITE? 
>>I need to invoke some functions only for the new INVITEs before transmit them.  
>>
>>Regards 
>>Daniele
>>
>>
>>**********************************************************************
>>The information in this message is confidential and may be legally
>>privileged. It is intended solely for the addressee. Access to this message
>>by anyone else is unauthorized. If you are not the intended recipient, any
>>disclosure, copying, or distribution of the message, or any action or
>>omission taken by you in reliance on it, is prohibited and may be unlawful.
>>Please immediately contact the sender if you have received this message in
>>error.
>>
>>**********************************************************************
>>
>>
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>Serusers mailing list
>>Serusers at iptel.org
>>http://mail.iptel.org/mailman/listinfo/serusers
> 
> 
> 
> **********************************************************************
> The information in this message is confidential and may be legally
> privileged. It is intended solely for the addressee. Access to this message
> by anyone else is unauthorized. If you are not the intended recipient, any
> disclosure, copying, or distribution of the message, or any action or
> omission taken by you in reliance on it, is prohibited and may be unlawful.
> Please immediately contact the sender if you have received this message in
> error.
> 
> **********************************************************************
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Serusers mailing list
> Serusers at iptel.org
> http://mail.iptel.org/mailman/listinfo/serusers

-- 
Voice System
http://www.voice-system.ro

**********************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message
by anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or
omission taken by you in reliance on it, is prohibited and may be unlawful.
Please immediately contact the sender if you have received this message in
error.

**********************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20050215/857bfd79/attachment.htm>


More information about the sr-users mailing list