[OpenSIPS-Users] Diversion information

[Bogdan-Andrei Iancu]

That's a typo - I ment failure route :) .


Sent from Samsung Mobile

-------- Original message --------
From: Mike Claudi Pedersen <mike.pedersen at ipnordic.dk> 
Date:08/04/2014  08:10  (GMT+01:00) 
To: Bogdan-Andrei Iancu <bogdan at opensips.org> 
Subject: Re: [OpenSIPS-Users] Diversion information 

what exactly do you mean with fsilutr ? i cant seem to find that route and the could you given an exact example of the syntax of the $di variable when i need to call it, im not sure what you mean by $(<reply>di) what could be where <reply> is?. sorry for the trouble i'm relatively new to this, and trying to do a school project on openSIPS


2014-04-07 13:08 GMT+02:00 Bogdan-Andrei Iancu <bogdan at opensips.org>:
Once again, if you get the Diversion header in the 300 reply, you can access it from fsilutr route via $(<reply>di) variable.

Regards,
Bogdan


Sent from Samsung Mobile


-------- Original message --------
From: Mike Claudi Pedersen 
Date:07/04/2014 13:37 (GMT+02:00) 
To: Bogdan-Andrei Iancu 
Subject: Re: [OpenSIPS-Users] Diversion information 

i have tried to call the variable $di from various routes now, they are all returning NULL? im not usre if it is my test setup that is failing but i have 2 test numbers 1000 and 1001.. on 1001 i have a permanent forward to 1000 and i then call 1001 from 1000, and get redirected to 1000.. shouldnt this generate a diversion header. when i trace it, it sure looks like its being generated, but i simply cant call this value from anywhere i only wanna use it for the purpose of showing the original caller in case of redirected calls.



2014-04-07 11:25 GMT+02:00 Mike Claudi Pedersen <mike.pedersen at ipnordic.dk>:
first time i encounter any diversion info is when i get the 302 moved temporarily, and the next sip message is an invite? so i would assume that it is a request ? 


2014-04-07 11:16 GMT+02:00 Bogdan-Andrei Iancu <bogdan at opensips.org>:

Hello Mike,

Once again, it depends in what kind of SIP messages you get the "diversion info" - if you get it into a requests, you can handle it in the main route; but if you get in replies, you need to to do it in failure route or reply route.


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 07.04.2014 10:53, kostenftw wrote:
okay.. if i want to make an exception that only handles calls with diversion
info i should do it in one of those routes ? right now i'm handling all of
my calls in the same route



--
View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Diversion-information-tp7590569p7590604.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users






-- 
Med venlig hilsen
ipnordic A/S

Mike Claudi Pedersen
Tekniker

Telefon: 79301033
www.ipnordic.dk



-- 
Med venlig hilsen
ipnordic A/S

Mike Claudi Pedersen
Tekniker

Telefon: 79301033
www.ipnordic.dk



-- 
Med venlig hilsen
ipnordic A/S

Mike Claudi Pedersen
Tekniker

Telefon: 79301033
www.ipnordic.dk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20140408/77d015c3/attachment-0001.htm>