|
From: Peeyush S. <Pee...@ma...> - 2014-02-13 13:22:43
|
That is fine, however based on different messages type I have created different responses. Like for an example in CCA-I, I have Default-EPS-Bearer-QoS and in CCR-U I have Charging-Rule-Install and in CCR-T is simply used to terminate session. I want to send 2 initial messages from PGW and then 1 update and then suppose 1 terminate then again few initiates. So based on the CCR-Type can seagull pick the message and send the corresponding response? Like for 2 initial the 2 CCA-I with default-eps-bearer-qos and then for the update with the CCA-U with Charging-Rule-Install. Regards, Peeyush Sharma From: Konstantin Tyurin [mailto:kt...@am...] Sent: Thursday, February 13, 2014 6:47 PM To: Peeyush Sharma; gul...@li... Subject: RE: [Seagull-users] Can seagull identify Gx Diameter messages baesd on their type and send response based on it CC-Request-Type AVP value indicates if it's initial, update or terminate. You can get the value from request and put it to response. Regards, Konstantin. From: Peeyush Sharma [mailto:Pee...@ma...] Sent: Thursday, February 13, 2014 5:12 PM To: gul...@li...<mailto:gul...@li...> Subject: [Seagull-users] Can seagull identify Gx Diameter messages baesd on their type and send response based on it Hi All, I am trying to create a scenario where I need to simulate PCRF(Gx diameter) using seagull. Does seagull provide us the functionality to different CCR messages based on their types like CCR-Initial, CCR-Update and CCR-Terminate. Can I implement something like whenever I am getting a CCR-Initial request then my seagull should respond with the CCA-I message and when I send update then CCA-U should go and similarly for CCR-T. I have composed in 1 scenario file where I have created responses for all CCR-I,U,T. Now based on the type of CCR message it should out of the available response message and should send the same. I want to implement this for multiple IP-CAN session with different session-Ids Regards, Peeyush Sharma This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp |